<commit_before>defmodule Mix.Tasks.Compile.App do
  use Mix.Task

  @recursive true

  @moduledoc """
  Writes an .app file.

  An `.app` file is a file containing Erlang terms that defines
  your application. Mix automatically generates this file based on
  your `mix.exs` configuration.

  In order to generate the file, Mix expects your application to
  have both `:app` and `:version` keys. Furthermore, you can configure
  the generated application by defining a `application` function in
  your `mix.exs` with the following options:

  * `:applications` - all applications your application depends
    on at runtime. For example, if your application depends on
    Erlang's `:crypto`, it needs to be added to this list. Most
    of your dependencies must be added as well (unless their are
    a development or test dependnecy). Mix and other tools use this
    list in order to properly boot your application dependencies
    before starting the application itself;

  * `:registered` - the name of all registered processes in the
    application. If your application defines a local GenServer
    with name `MyServer`, it is recommended to add `MyServer`
    to this list. It is mostly useful to detect conflicts in
    between applications that register the same names;

  * `:mod` - specify a module to invoke when the application
    is started, it must be in the format `{Mod, args}` where
    args is often an empty list. The module specified here must
    implement the callbacks defined by the `Application.Behaviour`
    behaviour;

  * `:env` - default values for the application environment.
    The application environment is one of the most common ways
    to configure applications;
<commit_msg>Fixed typo and improper use of their in documentation<commit_after>defmodule Mix.Tasks.Compile.App do
  use Mix.Task

  @recursive true

  @moduledoc """
  Writes an .app file.

  An `.app` file is a file containing Erlang terms that defines
  your application. Mix automatically generates this file based on
  your `mix.exs` configuration.

  In order to generate the file, Mix expects your application to
  have both `:app` and `:version` keys. Furthermore, you can configure
  the generated application by defining a `application` function in
  your `mix.exs` with the following options:

  * `:applications` - all applications your application depends
    on at runtime. For example, if your application depends on
    Erlang's `:crypto`, it needs to be added to this list. Most
    of your dependencies must be added as well (unless they're
    a development or test dependency). Mix and other tools use this
    list in order to properly boot your application dependencies
    before starting the application itself;

  * `:registered` - the name of all registered processes in the
    application. If your application defines a local GenServer
    with name `MyServer`, it is recommended to add `MyServer`
    to this list. It is mostly useful to detect conflicts in
    between applications that register the same names;

  * `:mod` - specify a module to invoke when the application
    is started, it must be in the format `{Mod, args}` where
    args is often an empty list. The module specified here must
    implement the callbacks defined by the `Application.Behaviour`
    behaviour;

  * `:env` - default values for the application environment.
    The application environment is one of the most common ways
    to configure applications;

{'fraction_non_alphanumeric': 0.05216138328530259, 'fraction_numerical': 0.0, 'mean_word_length': 3.6156914893617023, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3814381', 'n_tokens_mistral': 866, 'n_tokens_neox': 841, 'n_words': 481}