There are a number of ways to debug code in Elixir. In this chapter we will cover some of the more common ways of doing so. IO.inspect/2 What makes IO.inspect(item, opts \\ []) really useful in debugging is that it returns the item argument passed to it without affecting the behavior of the original code. Let’s see an example. (1..10) |> IO.inspect |> Enum.map(fn x -> x * 2 end) |> IO.inspect |> E
A new semester has started, which means it is time for a new Elixir release! This release brings quality of life improvements to the documentation, to error handling, to logger reporting, and to ExUnit, Elixir’s testing library. We are also glad to welcome Michał Muskała to the Elixir Core team. Prior to joining the team, he was a member of the Ecto team, he has made plenty of contributions to Eli
Elixir v1.6 includes new features, enhancements, and bug fixes. The main feature in this release is a code formatter. Important improvements can also be found in the standard library and in the Mix build tool. Code formatter The big feature in Elixir v1.6 is the addition of a code formatter and an accompanying mix format task that adds automatic formatting to your projects. The goal of the formatt
Today’s post marks the first in a new series bringing you the latest changes to the Elixir language. We’d love to hear from you about what you’d like to see in future posts so join the conversation on the Elixir Forum thread. So what’s in master? Let’s have a look: Disagreements about formatting are a thing of the past! As part of 1.6 we’ve added a code formatter to Elixir. The formatter is availa
In this blog post, we’ll talk about property-based testing and sample data generation. We’ll cover what these are, why we want them in Elixir, and what are are plans for the future. If you want to use the features discussed here or you want to read more formal documentation, head over to stream_data, which is a library that currently provides both features (albeit in beta form) and which is where
Elixir v1.5 includes new features, enhancements, and bug fixes. While Elixir v1.4 focused on tools for concurrency and scalability, Elixir v1.5 brings many improvements to the developer experience and quality of life. As we will see, many of those are powered by the latest Erlang/OTP 20. This is also the last Elixir release that supports Erlang/OTP 18. Note: this announcement contains asciinema sn
Elixir v1.4 brings new features, enhancements and bug fixes. The most notable changes are the addition of the Registry module, the Task.async_stream/3 and Task.async_stream/5 function which aid developers in writing concurrent software, and the new application inference and commands added to Mix. In this post we will cover the main additions. The complete release notes are also available. Registry
EEx v1.6.5 EEx View Source EEx stands for Embedded Elixir. It allows you to embed Elixir code inside a string in a robust way. iex> EEx.eval_string "foo <%= bar %>", [bar: "baz"] "foo baz" API This module provides 3 main APIs for you to use: Evaluate a string (eval_string) or a file (eval_file) directly. This is the simplest API to use but also the slowest, since the code is evaluated and not comp
Mix v1.6.5 mix escript.build View Source Builds an escript for the project. An escript is an executable that can be invoked from the command line. An escript can run on any machine that has Erlang installed and by default does not require Elixir to be installed, as Elixir is embedded as part of the escript. This task guarantees the project and its dependencies are compiled and packages them inside
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く