All currently open bugs related to Elixir are listed in the issues tracker.
The Elixir team uses the issues tracker to focus on actionable items,
including planned enhancements in the short and medium term. We also do
our best to label entries for clarity and to ease collaboration.
Our actionable item policy has some important consequences, such as:
Proposing new features as well as requests for support, help, and
guidance must be done in their own spaces, detailed next.
Issues we have identified to be outside of Elixir's scope,
such as an upstream bug, will be closed (and requested to be moved
elsewhere if appropriate).
We actively close unrelated and non-actionable issues to keep the
issues tracker tidy. If you believe we got something wrong, drop a
comment and we can always reopen the issue.
By keeping the overall issues tracker tidy and organized, the community
can easily peek at what is coming in new releases and also get involved
by commenting on existing issues and submitting pull requests. Please
remember to keep the tone positive and be kind! For more information,
see the Code of Conduct.
Discussions, support, and help
For general discussions, support, and help, please use the community
spaces listed on the sidebar of the Elixir website,
such as forums, chat platforms, etc, where the wider community will be available
to help you.
Once you are ready, you can submit your proposal to the Elixir Core
mailing list, either through the web interface or by subscribing to
it at [email protected]. Remember to include
a clear problem description, compare the proposed solution to existing
alternatives in the Elixir ecosystem (and in other languages if possible),
and consider the potential impact your changes will have on the codebase and
community.
Once a proposal is accepted, it will be added to the issue tracker.
Features and bug fixes that have already been merged and will be included
in the next release are then "closed" and added to the changelog
before release.
In case you want to use this Elixir version as your system version,
you need to add the bin directory to your PATH environment variable.
When updating the repository, you may want to run make clean before
recompiling. For deterministic builds, you should set the environment
variable ERL_COMPILER_OPTIONS=deterministic.
Contributing
Contributions to Elixir are always welcome! Before you get started, please check
out our CONTRIBUTING.md file. There you will find detailed
guidelines on how to set up your environment, run the test suite, format your
code, and submit pull requests.
Note you must disclose the use of coding agents and AI written code in your
contributions. See the "Using AI and coding agents" in CONTRIBUTING.md.
Что это?Elixir — это язык программирования, созданный для разработки масштабируемых и удобных в сопровождении приложений, который работает на виртуальной машине Erlang (BEAM).
Это полноценный язык или фреймворк поверх чего-то другого?Это полноценный язык программирования, который компилируется в байт-код виртуальной машины Erlang и перенимает модель параллелизма и отказоустойчивости BEAM.
Нужно ли мне сначала установить Erlang?Да, Erlang необходим до компиляции Elixir из исходного кода.
Есть ли подводные камни при сборке в Windows?Пользователям Windows стоит изучить отдельную статью с важными замечаниями о сборке Elixir из исходного кода на этой платформе.
Как мне добавить Elixir в PATH после сборки из исходного кода?Если вы хотите использовать эту собранную версию как системный Elixir, добавьте её каталог bin в переменную окружения PATH.
Как мне поддерживать сборку в чистоте после получения обновлений?При обновлении репозитория выполняйте make clean перед пересборкой, а для воспроизводимых сборок задайте ERLCOMPILEROPTIONS=deterministic.
Elixir — это язык программирования, созданный для разработки масштабируемых и удобных в сопровождении приложений, который работает на виртуальной машине Erlang (BEAM).