Gleam language adds built-in @deprecated, todo, and case-based pattern matching constructs

Gleam adds three small but high-leverage constructs that other languages typically handle with comments, linters, or macros. The @deprecated attribute is a compiler directive that surfaces migration hints when deprecated functions are called. This shifts the burden of deprecation warnings from library consumers to library authors, who can now encode upgrade paths directly in the code. The cost is a slight increase in annotation overhead for maintainers, but the benefit is compile-time enforcement of deprecation policies instead of runtime warnings or CI failures.

The todo keyword replaces comment-based reminders with a first-class language construct. Unlike comments, todo markers are visible to the compiler and tooling, enabling static analysis and IDE integration. This reduces the risk of stale todos lingering in codebases but requires engineers to adopt a new keyword instead of familiar comment syntax. The trade-off is minimal for new projects but may feel disruptive for teams migrating existing codebases with extensive comment-based todos.

Gleam consolidates all conditional logic, list deconstruction, and error handling into case expressions. This simplifies the language by eliminating separate constructs for if-else, switch, and pattern matching. The cost is reduced flexibility for engineers accustomed to language-specific idioms like Elixir’s multi-clause functions or Go’s type switches. However, the uniformity of case expressions may improve readability for teams working across multiple BEAM languages, as the same construct handles all branching logic.

Gleam’s design prioritizes compile-time safety over runtime flexibility. The absence of exceptions and null values forces engineers to handle errors and absent values explicitly using Options and Results. This eliminates entire classes of runtime errors but requires upfront investment in learning the type system. The trade-off is most visible in interoperability: Gleam code calling into other BEAM languages may need to wrap exceptions or nulls in Options or Results, adding a layer of conversion overhead.

The language’s simplicity comes from deliberate omissions. Generics are unconstrained, reducing complexity but limiting expressiveness for advanced use cases. Pattern matching is exhaustive, ensuring all cases are handled but requiring engineers to explicitly account for every possibility. These choices make Gleam easier to learn but may frustrate engineers who rely on more flexible constructs in other languages. The cost of adoption is lowest for greenfield projects and highest for teams deeply invested in idiomatic Elixir or Erlang.