AtomVM Daily: Weekly Recap - Closing the Gaps Between Native Code and Tooling
This week's three pull requests all address the same underlying issue: native functions and compiled Elixir constructs that worked at runtime but were invisible or unverified at the tooling level. The fixes add missing stubs, generate supported API lists directly from the source, and extend Elixir compilation support.
Duration: PT2M46S
Episode overview
This episode is a short developer briefing from AtomVM Daily.
It explains recent repository work in plain language.
- Show: AtomVM Daily
- Published: 2026-09-14T09:05:50Z
- Audio duration: PT2M46S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Welcome to AtomVM Daily, covering September 7th through September 14th, 2026.
Three pull request activity items this week, no additional commits. All three came from bettio, and all three circle back to a single theme: making AtomVM's actual capabilities match what its tooling and documentation claim.
Let's start with the core problem. Pull request 2394 found that a number of standard library functions in Erlang and Elixir are implemented natively, registered internally, but had no matching export or stub. That meant tools like beam lib, ExDoc, edoc, and Dialyzer couldn't see them, even though the functions were…
Pull request 2395 tackles the same blind spot from the build side. Build tools have been checking a project's calls against hand-maintained support lists baked into the tools themselves, meaning those lists reflected whatever version of the tool a developer had installed, not the actual AtomVM runtime. This change…
Pull request 2396 rounds out the week with an Elixir compilation addition, handling how the Elixir compiler expands map field lookups, both the standard inline form and the deprecated parenthesized form, into their underlying function calls. It's a narrower, more…
S…
Nearby episodes from AtomVM Daily
- Weekly Recap - Platform Reach and Data Correctness
- Weekly Recap - Locking Down TLS Security
- Weekly Recap - Platform Reach and Performance Groundwork
- Weekly Recap - Continuous Integration Gets a RISC-V Upgrade
- Weekly Recap - Standard Library Alignment
- Weekly Recap - Correctness Fixes and Expanding the Runtime's Reach
- Weekly Recap - Hardening the Runtime, Filling in the Standard Library
- Weekly Recap - Correctness Fixes and Platform Hardening