v1.18-latest

Automated release for latest v1.18.

main-latest

Automated release for latest main.

v1.18.1

1. Enhancements

• [Kernel] Do not emit type violation warnings when comparing or matching against literals
• [Kernel] Do not validate clauses of private overridable functions

2. Bug fixes

Elixir

• [Code.Fragment] Ensure Code.Fragment.container_cursor_to_quoted/2 with :trailing_fragment parses expressions that were supported in previous versions
• [Kernel] Do not crash when typing violation is detected on dynamic dispatch
• [Kernel] Properly annotate the source for warnings emitted by the compiler with the @file annotation
• [Kernel] Properly annotate the source for warnings emitted by the type system with the @file annotation
• [Kernel] Remove :no_parens metadata when using capture with arity on all cases
• [Kernel] Ensure diagnostic traces are kept backwards compatible

ExUnit

• [ExUnit.Case] Ensure async groups do not run concurrenly while the test suite is still loading
• [ExUnit.Case] Ensure --repeat-until-failure can be combined with groups

Mix

• [mix compile.elixir] Store compilation results if compilation fails due to --warnings-as-errors
• [mix deps.loadpaths] Add build lock
• [mix escript.build] Ensure build succeeds when protocol consolidation is disabled
• [Mix.Shell] Ensure encoding is properly respected on Windows and Unix systems

v1.18.0

https://elixir-lang.org/blog/2024/12/19/elixir-v1-18-0-released/

Elixir v1.18 is an impressive release with improvements across the two main efforts happening within the Elixir ecosystem right now: set-theoretic types and language servers. It also comes with built-in JSON support and adds new capabilities to its unit testing library. Here is a quick break down.

Type system improvements

The most exciting change in Elixir v1.18 is type checking of function calls, alongside gradual inference of patterns and return types. To understand how this will impact your programs, consider the following code in "lib/user.ex":

defmodule User do
  defstruct [:age, :car_choice]

  def drive(%User{age: age, car_choice: car}, car_choices) when age >= 18 do
    if car in car_choices do
      {:ok, car}
    else
      {:error, :no_choice}
    end
  end

  def drive(%User{}, _car_choices) do
    {:error, :not_allowed}
  end
end

Elixir's type system will infer that the drive/2 function expects a %User{} struct and returns either {:ok, dynamic()}, {:error, :no_choice}, or {:error, :not_allowed}.

Therefore, the following code in a separate module (either in a separate or the same file), should emit a violation, due to an invalid argument:

User.drive({:ok, %User{}}, car_choices)

Here is the warning:

    warning: incompatible types given to User.drive/2:

        User.drive({:ok, %User{age: nil, car_choice: nil}}, car_choices)

    given types:

        {:ok, %User{age: nil, car_choice: nil}}, empty_list()

    but expected one of:

        dynamic(%User{age: term(), car_choice: term()}), dynamic()

    where "car_choices" was given the type:

        # type: empty_list()
        # from: lib/foo.ex:21:17
        car_choices = []

    typing violation found at:
    │
 22 │     User.drive({:ok, %User{}}, car_choices)
    │          ~
    │
    └─ lib/foo.ex:22:10: Example.run/0

The mismatched arguments are shown in red, if your terminal supports ANSI coloring.

And the next snippet will warn because the :error clause will never match, as that's not a valid return type of the User.drive/2 call:

case User.drive(user, car_choices) do
  {:ok, car} -> car
  :error -> Logger.error("User cannot drive")
end

And here is the warning:

    warning: the following clause will never match:

        :error

    because it attempts to match on the result of:

        User.drive(user, car_choices)

    which has type:

        dynamic({:ok, term()} or {:error, :no_choice} or {:error, :not_allowed})

    typing violation found at:
    │
 26 │       :error -> Logger.error("User cannot drive")
    │       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    │
    └─ lib/foo.ex:26: Example.run/0

For more details on typing inference and the trade-offs made by the Elixir team, see our official documentation.

There are many other improvements to the type system, which we will go in detail within the official release. Meanwhile, here is a list summary of the overall improvements done to the type system:

• Type inference of patterns (typing inference of guards will be part of an upcoming release)

• Type checking of all language constructs, including local and remote calls, except for, with, and closures

• Type checking of all functions inlined by the compiler found in Kernel

• Type checking of all conversion functions inlined by the compiler

• Support for tuples and lists as composite types as well as type checking of their basic operations

• Detection of clauses and patterns that will never match from case, cond, and =

• Detection of unused clauses in private functions

ExUnit improvements

ExUnit now supports parameterized tests to run the same test module multiple times under different parameters.

For example, Elixir ships a local, decentralized and scalable key-value process storage called Registry. The registry can be partitioned and its implementation differs depending if partitioning is enabled or not. Therefore, during tests, we want to ensure both modes are exercised. With Elixir v1.18, we can achieve this by writing:

defmodule Registry.Test do
  use ExUnit.Case,
    async: true,
    parameterize: [
      %{partitions: 1},
      %{partitions: 8}
    ]

  # ... the actual tests ...
end

ExUnit parameterizes whole test modules. If your modules are configured to run concurrently, as above, so will the parameterized ones.

ExUnit also comes with the ability of specifying test groups. While ExUnit supports running tests concurrently, those tests must not have shared state between them. However, in large applications, it may be common for some tests to depend on some shared state, and other tests to depend on a completely separate state. For example, part of your tests may depend on Cassandra, while others depend on Redis. Prior to Elixir v1.18, these tests could not run concurrently, but in v1.18 they might as long as they are assigned to different groups. Tests modules within the same group do not run concurrently, but across groups, they might.

With features like async tests, suite partitioning, and now grouping, Elixir developers have plenty of flexibility to make the most use of their machine resources, both in development and in CI.

mix format --migrate

The mix format command now supports an explicit --migrate flag, which will convert constructs that have been deprecated in Elixir to their latest version. Because this flag rewrites the AST, it is not guaranteed the migrated format will always be valid when used in combination with macros that also perform AST rewriting.

As of this release, the following migrations are executed:

• Normalize parens in bitstring modifiers - it removes unnecessary parentheses in known bitstring modifiers, for example <<foo::binary()>> becomes <<foo::binary>>, or adds parentheses for custom modifiers, where <<foo::custom_type>> becomes <<foo::custom_type()>>.

• Charlists as sigils - formats charlists as ~c sigils, for example 'foo' becomes ~c"foo".

• unless as negated ifs - rewrites unless expressions using if with a negated condition, for example unless foo do becomes if !foo do.

More migrations may be added in future releases.

JSON support

This release includes official support for JSON encoding and decoding.

Both encoder and decoder fully conform to RFC 8259 and ECMA 404 standards.

Encoding

Encoding can be done via JSON.encode!/1 and JSON.encode_to_iodata!/1 functions. The default encoding rules are applied as follows:

Elixir	JSON
integer() | float()	Number
true | false	Boolean
nil	Null
binary()	String
atom()	String
list()	Array
%{binary() => _}	Object
%{atom() => _}	Object
%{integer() => _}	Object

You may also implement the JSON.Encoder protocol for custom data structures. Elixir already implements the protocol for all Calendar types.

If you have a struct, you can derive the implementation of the JSON.Encoder by specifying which fields should be encoded to JSON:

  @derive {JSON.Encoder, only: [...]}
  defstruct ...

Decoding

Decoding can be done via JSON.decode/2 and JSON.decode!/2 functions. The default decoding rules are applied as follows:

JSON	Elixir
Number	integer() | float()
Boolean	true | false
Null	nil
String	binary()
Object	%{binary() => _}

Language server listeners

4 months ago, we welcomed the Official Language Server team, with the goal of unifying the efforts behind code intelligence, tools, and editors in Elixir. Elixir v1.18 brings new features on this front by introducing locks and listeners to its compilation. Let's understand what it means.

At the moment, all language server implementations have their own compilation environment. This means that your project and dependencies during development are compiled once, for your own use, and then again for the language server. This duplicate effort could cause the language server experience to lag, when it could be relying on the already compiled artifacts of your project.

This release address by introducing a compiler lock, ensuring that only a single operating system process running Elixir compiles your project at a given moment, and by providing the ability for one operating system process to listen to the compilation results of others. In other words, different Elixir instances can now communicate over the same compilation build, instead of racing each other.

These enhancements do not only improve editor tooling, but they also directly benefit projects like IEx and Phoenix. For example, you can invoke IEx.configure(auto_reload: true) and IEx will automatically reload modules changed elsewhere, either by a separate terminal or your IDE.

Potential incompatibilities

This release no longer supports WERL (a graphical user interface on Windows used by Erlang 25 and earlier). For a better user experience on Windows terminals, use Erlang/OTP 26+ (this is also the last Elixir release to support Erl...

v1.18.0-rc.0

1. Enhancements

Elixir

• [CLI] Add experimental PowerShell scripts for elixir, elixirc, and mix on Windows. Those provide a safer entry point for running Elixir from other platforms
• [Calendar] Add Duration.to_string/1
• [Code] Support several migration options in Code.format_string!/2
• [Code] Add parenthesis around -- and --- in Code.format_string!/2 to make precedence clearer
• [Code] Include more metadata in Code.string_to_quoted/2 when token_metadata: true to help compute ranges from the AST
• [Code.Fragment] Have :capture_arg as its own entry in Code.Fragment.surround_context/2
• [Config] Add Config.read_config/1
• [Enumerable] Add Enum.product_by/2 and Enum.sum_by/2
• [Exception] Add MissingApplicationsError exception to denote missing applications
• [Kernel] Update source code parsing to match UTS #55 latest recommendations. In particular, mixed script is allowed in identifiers as long as they are separate by underscores (_), such as http_сервер. Previously allowed highly restrictive identifiers, which mixed Latin and other scripts, such as the japanese word for t-shirt, Tシャツ, now require the underscore as well
• [Kernel] Warn on bidirectional confusability in identifiers
• [Kernel] Verify the type of the binary generators
• [Kernel] Track the type of tuples in patterns and inside elem/2
• [Kernel] Perform validation of root AST nodes in unquote and unquote_splicing to catch bugs earlier
• [Kernel] Add source, behaviour, and record information to Docs chunk metadata
• [Kernel] Support deterministic builds in tandem with Erlang by setting ERL_COMPILER_OPTIONS=deterministic. Keep in mind deterministic builds strip source and other compile time information, which may be relevant for programs
• [Kernel] Allow aliases and imports to be enabled conditionally in module body
• [List] Add List.ends_with?/2
• [Macro] Improve dbg handling of if/2, with/1 and of code blocks
• [Macro] Add Macro.struct_info!/2 to return struct information mirroring mod.__info__(:struct)
• [Registry] Add Registry.lock/3 for local locking
• [PartitionSupervisor] Add PartitionSupervisor.resize!/2 to resize the number of partitions in a supervisor (up to the limit it was started with)
• [Process] Handle arbitrarily high integer values in Process.sleep/1
• [Protocol] Add @undefined_impl_description to customize error message when an implementation is undefined
• [Protocol] Add __deriving__/1 as optional macro callback to Protocol, no longer requiring empty implementations
• [String] Inspect special whitespace and zero-width characters using their Unicode representation
• [String] Update Unicode to 16.0

ExUnit

• [ExUnit] Support parameterized tests on ExUnit.Case
• [ExUnit] Support test groups: tests in the same group never run concurrently
• [ExUnit.Case] Add test_pid as a tag

IEx

• [IEx] Add :dot_iex support to IEx.configure/1
• [IEx] Add report for normal/shutdown exits in IEx

Mix

• [mix compile] Ensure only a single operating system process can compile at a given time
• [mix deps.get] Ensure only a single operating system process can fetch deps at a given time
• [mix format] Add mix format --migrate to migrate from deprecated functionality
• [mix format] Add new options and metadata to improve formatting applying by editors and other environments
• [mix test] Taint failure manifest if requiring or compiling tests fail
• [Mix.Project] Add a :listeners configuration to listen to compilation events from the current and other operating system processes
• [Mix.Task.Compiler] Add API for fetching all persisted compiler diagnostics
• [Mix.Task.Compiler] Add API for fetching all compiler tasks

2. Bug fixes

Elixir

• [Code] Fix delimiter metadata for single quoted atoms and remote calls in Code.string_to_quoted/2
• [Code.Formatter] Fix formatter adding extra escapes to quoted remote calls
• [Code.Fragment] Properly handle keyword keys as their own entry
• [Inspect.Algebra] Ensure next_break_fits respects line_length
• [Kernel] Validate AST on unquote and unquote_splicing to provide better error reports instead of failing too late inside the compiler
• [Module] Include module attribute line and name when tracing its aliases
• [Stream] Do not halt streams twice in Stream.transform/5
• [URI] Fix a bug when a schemaless URI is given to URI.merge/2

ExUnit

• [ExUnit.Assertions] Raise if guards are used in assert/1 with =
• [ExUnit.Assertions] Format inserted/deleted maps in list assertions

IEx

• [IEx.Helpers] IEx.Helpers.recompile/0 will reload modules changed by other operating system processes

Mix

• [mix compile] Ensure warnings from external resources are emitted with --all-warnings when files do not change
• [mix deps.compile] Fix escaping issues when invoking rebar3 in some cases
• [mix escript] Fix escript layout and support storing priv directories
• [mix release] Make .app files deterministic in releases
• [Mix.Shell] Fix Mix.Shell on Windows when outputting non UTF-8 characters

3. Soft deprecations (no warnings emitted)

Elixir

• [Inspect.Algebra] color/3 is deprecated in favor of color_doc/3
• [Inspect.Algebra] fold_doc/2 is deprecated in favor of fold/2
• [Kernel] Deprecate unless in favor of if. Use mix format --migrate to automate the migration
• [Macro] Macro.struct!/2 is deprecated in favor of Macro.struct_info!/2
• [Protocol] Defining __deriving__/3 inside the Any implementation is deprecated, derive it inside the protocol definition itself

4. Hard deprecations

EEx

• [EEx] <%# is deprecated in favor of <%!-- or <% #
• [EEx] c:EEx.handle_text/2 is deprecated in favor of c:EEx.handle_text/3

Elixir

• [Code] Setting :warnings_as_errors is deprecated via Code.put_compiler_option/2. This must not affect developers, as the :warnings_as_errors option is managed by Mix tasks, and not directly used via the Code module
• [Enumerable] Deprecate returning a two-arity function in Enumerable.slice/1
• [List] List.zip/1 is deprecated in favor of Enum.zip/1
• [Module] Deprecate Module.eval_quoted/3 in favor of Code.eval_quoted/3
• [Range] Deprecate inferring negative ranges on Range.new/2
• [Tuple] Tuple.append/2 is deprecated, use Tuple.insert_at/3 instead

Mix

• [mix cmd] Deprecate mix cmd --app APP in favor of mix do --app APP
• [Mix.Tasks.Compile] Deprecate compilers/0 in favor of Mix.Task.Compiler.compilers/0

v1.17.3

1. Bug fixes

Elixir

• [Duration] Fix parsing of fractional durations with non-positive seconds
• [Kernel] Do not attempt to group module warnings when they have a large context

IEx

• [IEx.Helpers] Properly reconsolidate protocols on recompile

Mix

• [mix compile.elixir] Do not verify modules twice
• [mix xref] Respect the --label option on stats and cycles

v1.17.2

1. Bug fixes

Logger

• [Logger.Translator] Fix logger crash when :gen_statem's format_status/2 returns non-tuple

Mix

• [mix deps.get] Fix regression when fetching a git repository with a :ref
• [mix release] Validate RELEASE_MODE and set ERRORLEVEL on .bat scripts
• [mix release] Fix invalid example in code comment inside the generated vm.args.eex

v1.17.1

1. Enhancements

Mix

• [mix compile.elixir] Do not run fixpoint computation on runtime dependencies. This should considerably improve compilation times for large projects when changing only one or two files

2. Bug fixes

EEx

• [EEx] Do not warn for assignment with blocks in EEx

Elixir

• [Kernel] Fix bug when using pinned variables inside with's else patterns
• [Kernel] Fix Dialyzer error when with else clause is calling a no_return function

ExUnit

• [ExUnit] Do not alternative sync/async suites on --repeat-until-failure

v1.17.0

https://elixir-lang.org/blog/2024/06/12/elixir-v1-17-0-released/

This release includes type inference of patterns to provide warnings for an initial set of constructs (binaries, maps, and atoms) within the same function. It also includes a new Duration data type to interact with Calendar types, support for Erlang/OTP 27, and many other improvements.

Warnings from gradual set-theoretic types

This release introduces gradual set-theoretic types to infer types from patterns and use them to type check programs, enabling the Elixir compiler to find faults and bugs in codebases without requiring changes to existing software. The underlying principles, theory, and roadmap of our work have been outlined in "The Design Principles of the Elixir Type System" by Giuseppe Castagna, Guillaume Duboc, José Valim.

At the moment, Elixir developers will interact with set-theoretic types only through warnings found by the type system. The current implementation models all data types in the language:

• binary(), integer(), float(), pid(), port(), reference() - these types are indivisible. This means both 1 and 13 get the same integer() type.

• atom() - it represents all atoms and it is divisible. For instance, the atom :foo and :hello_world are also valid (distinct) types.

• map() and structs - maps can be "closed" or "open". Closed maps only allow the specified keys, such as %{key: atom(), value: integer()}. Open maps support any other keys in addition to the ones listed and their definition starts with ..., such as %{..., key: atom(), value: integer()}. Structs are closed maps with the __struct__ key.

• tuple(), list(), and function() - currently they are modelled as indivisible types. The next Elixir versions will also introduce fine-grained support to them.

We focused on atoms and maps on this initial release as they are respectively the simplest and the most complex types representations, so we can stress the performance of the type system and quality of error messages. Modelling these types will also provide the most immediate benefits to Elixir developers. Assuming there is a variable named user, holding a %User{} struct with an address field, Elixir v1.17 will emit the following warnings at compile-time:

• Pattern matching against a map or a struct that does not have the given key, such as %{adress: ...} = user (notice address vs adress)

• Accessing a key on a map or a struct that does not have the given key, such as user.adress

• Updating a struct or a map that does not define the given key, such as %{user | adress: ...}

• Invoking a function on non-modules, such as user.address()

• Capturing a function on non-modules, such as &user.address/0

• Attempting to invoke to call an anonymous function without an actual function, such as user.()

• Performing structural comparisons with structs, such as my_date < ~D[2010-04-17]

• Performing structural comparisons between non-overlapping types, such as integer >= string

• Building and pattern matching on binaries without the relevant specifiers, such as <<name>> (this warns because by default it expects an integer, it should have been <<name::binary>> instead)

• Attempting to rescue an undefined exception or a struct that is not an exception

• Accessing a field that is not defined in a rescued exception

These new warnings help Elixir developers find bugs earlier and give more confidence when refactoring code, especially around maps and structs. While some of these warnings were emitted in the past, they were discovered using syntax analysis. The new warnings are more reliable, precise, and with better error messages. Keep in mind, however, that the Elixir typechecker only infers types from patterns within the same function at the moment. Analysis from guards and across function boundaries will be added in future relases. For more details, see our new reference document on gradual set-theoretic types.

The type system was made possible thanks to a partnership between CNRS and Remote. The development work is currently sponsored by Fresha, Starfish*, and Dashbit.

Erlang/OTP support

This release adds support for Erlang/OTP 27 and drops support for Erlang/OTP 24. We recommend Elixir developers to migrate to Erlang/OTP 26 or later, especially on Windows. Support for WERL (a graphical user interface for the Erlang terminal on Windows) will be removed in Elixir v1.18.

Adding Duration and shift/2 functions

Elixir introduces the Duration data type and APIs to shift dates, times, and date times by a given duration, considering different calendars and time zones.

iex> Date.shift(~D[2016-01-31], month: 2)
~D[2016-03-31]

Note the operation is called shift (instead of add) since working with durations does not obey properties such as associativity. For instance, adding one month and then one month does not give the same result as adding two months:

iex> ~D[2016-01-31] |> Date.shift(month: 1) |> Date.shift(month: 1)
~D[2016-03-29]

Still, durations are essential for building intervals, recurring events, and modelling scheduling complexities found in the world around us. For DateTimes, Elixir will correctly deal with time zone changes (such as Daylight Saving Time), but provisions are also available in case you want to surface conflicts (for example, you shifted to a wall clock that does not exist, because the clock has been moved forward by one hour). See DateTime.shift/2 for examples.

Finally, a new Kernel.to_timeout/1 function has been added, which helps developers normalize durations and integers to a timeout used by Process APIs. For example, to send a message after one hour, one can now write:

Process.send_after(pid, :wake_up, to_timeout(hour: 1))

v1.17.0 (2024-06-12)

1. Enhancements

Elixir

• [Access] Add Access.find/1 that mirrors Enum.find/2
• [Code] Support cursor inside fn/rescue/catch/else/after inside Code.Fragment.container_cursor_to_quoted/2
• [Date] Add Date.shift/2 to shift dates with duration and calendar-specific semantics
• [Date] Allow Date to accept years outside of -9999..9999 range
• [DateTime] Add DateTime.shift/2 to shift datetimes with duration and calendar-specific semantics
• [Duration] Add a new Duration data type
• [GenServer] Add c:GenServer.format_status/1 callback
• [Kernel] Add Kernel.get_in/1 with safe nil-handling for access and structs
• [Kernel] Add Kernel.is_non_struct_map/1 guard
• [Kernel] Add Kernel.to_timeout/1
• [Kernel] Emit warnings for undefined functions from modules defined within the same context as the caller code
• [Kernel] Support integers in uppercase sigils
• [Keyword] Add Keyword.intersect/2-3 to mirror the Map API
• [Macro] Add Macro.Env.define_alias/4, Macro.Env.define_import/4, Macro.Env.define_require/4, Macro.Env.expand_alias/4, Macro.Env.expand_import/5, and Macro.Env.expand_require/6 to aid the implementation of language servers and embedded languages
• [NaiveDateTime] Add NaiveDateTime.shift/2 to shift naive datetimes with duration and calendar-specific semantics
• [Process] Add Process.set_label/1
• [String] Add String.byte_slice/3 to slice a string to a maximum number of bytes while keeping it UTF-8 encoded
• [System] Support use_stdio: false in System.cmd/3 and System.shell/2
• [Time] Add Time.shift/2 to shift times with duration and calendar-specific semantics

ExUnit

• [ExUnit] Propagate the test process itself as a caller in start_supervised
• [ExUnit] Include max cases in ExUnit reports

IEx

• [IEx.Helpers] Warns if recompile was called and the current working directory changed
• [IEx.Helpers] Add c/0 as an alias to continue/0
• [IEx.Pry] Add IEx.Pry.annotate_quoted/3 to annotate a quoted expression with pry breakpoints

Logger

• [Logger] Format :gen_statem reports using Elixir data structures
• [Logger] Include process label in logger events

Mix

• [mix deps] Add :depth option to Mix.SCM.Git, thus supporting shallow clones of Git dependencies
• [mix deps] Warn if :optional is used in combination with :in_umbrella
• [mix deps.get] Do not add optional dependency requirements if its parent dep was skipped
• [mix deps.tree] Add --umbrella-only to mix deps.tree
• [mix profile.tprof] Add a new profiler, available on Erlang/OTP 27+, which can measure count, time, and heap usage
• [mix test] Add mix test --breakpoints that sets up a breakpoint before each test that will run
• [mix test] Add mix test --repeat-until-failure to rerun tests until a failure occurs
• [mix test] Add mix test --slowest-modules to print slowest modules based on all of the tests they hold
• [mix test] Generate cover HTML files in parallel

2. Bug fixes

Elixir

• [bin/elixir.bat] Improve handling of quotes and exclamation marks in flags
• [Code] Address a bug where AST nodes for (a -> b) were not wrapped as part of the literal encoder
• [Kernel] Resolve inconsistencies of how .. and ... are handled at the AST level
• [Kernel] Fix parsing precedence of ambiguous operators followed by containers
• [Kernel] Do not expand code in quote bind_quoted: ... twice
• [Kernel] Respect :line property when :file is given as option to quote
• [Kernel] Do not crash on Macro.escape/2 when passing a quote triplet without valid meta
• [Kernel] Avoid double tracing events when capturing a functi...

v1.17.0-rc.1

1. Enhancements

Elixir

• [Duration] Add Duration.to_iso8601/1 and Duration.from_iso8601/1
• [Keyword] Add Keyword.intersect/2-3 to mirror the Map API

Mix

• [mix profile.tprof] Add a new profiler, available on Erlang/OTP 27+, which can measure count, time, and heap usage
• [mix test] Generate cover HTML files in parallel

2. Bug fixes

Elixir

• [Kernel] Avoid double tracing events when capturing a function
• [Kernel] Fix a bug where captured arguments would conflict when a capture included a macro that also used captures

3. Soft deprecations

Mix

• [mix profile.cprof] Deprecated in favor of the new mix profile.tprof
• [mix profile.eprof] Deprecated in favor of the new mix profile.tprof