Elixir v1.20 released: now a gradually typed language
Elixir v1.20 introduces a gradually typed language feature, allowing type inference and checking without requiring type annotations. This update aims to enhance code reliability by identifying dead code and verified bugs efficiently. The new dynamic() type provides flexibility while maintaining developer-friendly error reporting.
- ▪Elixir v1.20 completes its first milestone in type system development, enabling type inference and gradual type checking.
- ▪The dynamic() type in Elixir allows for runtime type checking without introducing typing annotations.
- ▪Elixir's type system aims to minimize false positives while effectively identifying verified bugs in existing programs.
Hacker News (Front Page) files mainly under programming. We currently carry 993 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | The Elixir programming language |
| Canonical URL | https://elixir-lang.org/blog/2026/06/03/elixir-v1-20-0-released/ |
| Publication time | Wed, 03 Jun 2026 19:02:26 +0000 |
| Retrieval time | 2026-06-03T19:26:58.109Z |
| Last seen | 2026-06-03T19:26:58.109Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 2FUvhwo9uQC9 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
In 2022, we announced the effort to add set-theoretic types to Elixir. In June 2023, we published an award winning paper on Elixir’s type system design and said our work was transitioning from research to development. With Elixir v1.20, we have completed our first development milestone which is to perform type inference and gradually type check every Elixir program, without introducing type annotations. This means Elixir increasingly reports dead code and verified bugs: typing violations that are guaranteed to fail at runtime if executed. Elixir can find verified bugs in existing programs efficiently, without introducing developer overhead, and with an extremely low false positives rate.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Elixir programming language.
Discussion
0 commentsMore from The Elixir programming language
