The Wire · Showcase
ELIXIR PATCHES CALENDAR PERFORMANCE REGRESSION WHILE PHOENIX EXPANDS PLUG FLEXIBILITY
By RepoJournal · Filed · About Elixir & Phoenix
Elixir shipped a critical fix for Calendar.strftime/3 that regressed after a recent change, while Phoenix clarifies pipe_through to handle all plug forms.
The Elixir team fixed a performance regression in Calendar.strftime/3 [1] by switching to byte_size for pad leading in ASCII-guaranteed formats, restoring the speed lost after PR #15665. Alongside that fix, the core library landed typespec corrections for scoped macro counters [2], along with documentation and spec improvements for Code.Fragment [3] and Code modules [4]. Over on the Phoenix side, a reworked pull request [5] clarifies that pipe_through now accepts pipelines and all plug forms, not just module plugs with options. This closes a gap where developers couldn't easily compose flexible plug chains in router definitions. Five commits and 5 PRs across both repos keep the ecosystem tight.
One email a day. Unsubscribe in one click.
Keep up with Elixir & Phoenix in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Review and pull Calendar.strftime/3 fix if you use date formatting in hot paths elixir-lang/elixir [plan]
- → Check Phoenix router pipe_through usage once the new PR lands for clearer plug composition patterns phoenixframework/phoenix [monitor]
References
- [1] Fix Calendar.strftime/3 perfomance regression ↗ elixir-lang/elixir
- [2] Fix typespecs for scoped macro counters (#15705) elixir-lang/elixir
- [3] Fix Code.Fragment specs and docs (#15701) elixir-lang/elixir
- [4] Fix Code doc wordings and clarify (#15703) elixir-lang/elixir
- [5] Make pipe_through accepts pipelines and all plug forms ↗ phoenixframework/phoenix