$ the-wire · showcase
Base validators go SWAR, formatter output stabilizes
By RepoJournal · Filed · About Elixir & Phoenix · Composed from the cited sources · methodology
Elixir rewrote Base16/32/64 validation around SWAR word checks and restored a comment check that keeps mix format idempotent for inline tuple arguments.
Optimize Base validation with SWAR case folding and 8-byte streaming elixir-lang/elixir
Validation now case-folds with an ASCII `bor 0x20` (and the 8-byte `0x20202020202020` word form) and streams 8 bytes at a time via `<<c, w::56, rest::binary>>` instead of slicing binaries upfront, collapsing the high-bit gate and range mask into one branch. The PR reports it is faster, uses less memory, and shrinks `Elixir.Base.beam` by 14.5% (-31.1 KB).
Keep formatter output stable for comments inside tuple arguments elixir-lang/elixir
A call whose last argument is a tuple or bitstring is tested for a newline after the opening bracket to decide if it can start as `foo({`; the comment check (`eol_or_comments?`) dropped in #15893 is back, using comment metadata. Without it, the first `mix format` and the second picked different layouts.