Elixir (programming language)

Elixir
elixir programming language
Paradigmsmulti-paradigm: functional, concurrent, distributed, process-oriented
Designed byJosé Valim
First appeared25 May 2012; 14 years ago (2012-05-25)[1][2][3]
Stable release
1.20[4] Edit this on Wikidata / 3 June 2026; 4 days ago (3 June 2026)
Typing disciplinedynamic, strong, gradual since version 1.20[5]
PlatformErlang
LicenseApache License 2.0[6]
Filename extensions.ex, .exs
Websiteelixir-lang.org
Influenced by
Clojure, Erlang, Ruby
Influenced
Gleam, LFE

Elixir is a functional, concurrent, high-level general-purpose programming language that runs on the BEAM virtual machine, which is also used to implement the Erlang programming language.[7] Elixir builds on top of Erlang and shares the same abstractions for building distributed, fault-tolerant applications. Elixir also provides tooling and an extensible design. The latter is supported by compile-time metaprogramming with macros and polymorphism via protocols.[8]

The community organizes yearly events in the United States,[9] Europe,[10] and Japan,[11] as well as minor local events and conferences.[12][13]

History

José Valim created the Elixir programming language as a research and development project at Plataformatec. His goals were to enable higher extensibility and productivity in the Erlang VM while maintaining compatibility with Erlang's ecosystem.[14][15]

Elixir is aimed at large-scale sites and apps. It uses features of Ruby, Erlang, and Clojure to develop a high-concurrency and low-latency language. It was designed to handle large data volumes. Elixir is also used in telecommunications, e-commerce, and finance.[16]

In 2021, the Numerical Elixir effort was announced with the goal of bringing machine learning, neural networks, GPU compilation, data processing, and computational notebooks to the Elixir ecosystem.[17]

Features

Examples

The following examples can be run in an iex shell or saved in a file and run from the command line by typing elixir <filename>.

Classic Hello world example:

iex> IO.puts("Hello World!")
Hello World!

Pipe operator:

iex> "Elixir" |> String.graphemes() |> Enum.frequencies()
%{"E" => 1, "i" => 2, "l" => 1, "r" => 1, "x" => 1}

iex> %{values: 1..5} |> Map.get(:values) |> Enum.map(& &1 * 2)
[2, 4, 6, 8, 10]

iex> %{values: 1..5} |> Map.get(:values) |> Enum.map(& &1 * 2) |> Enum.sum()
30

Pattern matching (a.k.a. destructuring):

iex> %{left: x} = %{left: 5, right: 8}
iex> x
5

iex> {:ok, [_ | rest]} = {:ok, [1, 2, 3]}
iex> rest
[2, 3]

Pattern matching with multiple clauses:

iex> case File.read("path/to/file") do
iex>   {:ok, contents} -> IO.puts("found file: #{contents}")
iex>   {:error, reason} -> IO.puts("missing file: #{reason}")
iex> end

List comprehension:

iex> for n <- 1..5, rem(n, 2) == 1, do: n*n
[1, 9, 25]

Asynchronously reading files with streams:

1..5
|> Task.async_stream(&File.read!("#{&1}.txt"))
|> Stream.filter(fn {:ok, contents} -> String.trim(contents) != "" end)
|> Enum.join("\n")

Multiple function bodies with guards:

def fib(n) when n in [0, 1], do: n
def fib(n), do: fib(n-2) + fib(n-1)

Relational databases with the Ecto library:

schema "weather" do
  field :city     # Defaults to type :string
  field :temp_lo, :integer
  field :temp_hi, :integer
  field :prcp,    :float, default: 0.0
end

Weather |> where(city: "Kraków") |> order_by(:temp_lo) |> limit(10) |> Repo.all

Sequentially spawning a thousand processes:

for num <- 1..1000, do: spawn fn -> IO.puts("#{num * 2}") end

Asynchronously performing a task:

task = Task.async fn -> perform_complex_action() end
other_time_consuming_action()
Task.await task

[citation needed]

See also

References

  1. ^ Valim, José (25 May 2012). "Elixir v0.5.0 released". elixir-lang. Retrieved 22 January 2026.
  2. ^ "Elixir's Evolution: History and Ecosystem". Software Patterns Lexicon. 23 November 2024. Archived from the original on 22 January 2026. Retrieved 22 January 2026.
  3. ^ Woo, Jiahao (15 January 2024). "The Story of Elixir". OSS History. Archived from the original on 15 January 2024. Retrieved 22 January 2026.
  4. ^ https://github.com/elixir-lang/elixir/releases/. {{cite web}}: Missing or empty |title= (help)
  5. ^ https://elixir-lang.org/blog/2026/06/03/elixir-v1-20-0-released/
  6. ^ "elixir/LICENSE at master · elixir-lang/elixir · GitHub". GitHub.
  7. ^ "Most Popular Programming Languages of 2018 - Elite Infoworld Blog". 30 March 2018. Archived from the original on 9 May 2018. Retrieved 8 May 2018.
  8. ^ a b c d e f g "Elixir". elixir-lang. Retrieved 17 February 2013.
  9. ^ "ElixirConf". Retrieved 11 July 2018.
  10. ^ "ElixirConf". Retrieved 11 July 2018.
  11. ^ "Erlang & Elixir Fest". Archived from the original on 30 March 2019. Retrieved 18 February 2019.
  12. ^ "Elixir LDN". Archived from the original on 12 July 2018. Retrieved 12 July 2018.
  13. ^ "EMPEX - Empire State Elixir Conference". Retrieved 12 July 2018.
  14. ^ Elixir - A modern approach to programming for the Erlang VM. Retrieved 17 February 2013.
  15. ^ José Valim - ElixirConf EU 2017 Keynote. Archived from the original on 17 November 2021. Retrieved 14 July 2017.
  16. ^ "Behinde the code: The One Who Created Elixir". Retrieved 25 November 2019.
  17. ^ "Numerical Elixir (Nx)". GitHub. Retrieved 6 May 2024.
  18. ^ "Writing assertive code with Elixir". 24 September 2014. Retrieved 5 July 2018.
  19. ^ Loder, Wolfgang (12 May 2015). Erlang and Elixir for Imperative Programmers. "Chapter 16: Code Structuring Concepts", section title "Actor Model": Leanpub. Retrieved 7 July 2015.{{cite book}}: CS1 maint: location (link)
  20. ^ Wlaschin, Scott (May 2013). "Railway Oriented Programming". F# for Fun and Profit. Archived from the original on 30 January 2021. Retrieved 28 February 2021.

Further reading

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.