ElixirConf 2021 - Isaac Yonemoto - Zig (heart) Elixir

ElixirConf · 3K views · 2021 · 48:11

Open on YouTube

Functional programmingC, C++, Rust, Go & systems languagestalkdated

Why Hacker News recommends it

HN threads on Zig and Elixir link it as the creator's explanation of how Zig NIFs can behave nicely inside the BEAM.

What it is

Isaac Yonemoto's ElixirConf 2021 talk on Zigler, a library for writing Elixir NIFs in Zig. He looks at its internals and how it bridges the two languages while keeping the NIFs well behaved on the BEAM.

Recommended by 2 HN commenters across 2 different months, 2021 to 2025.

What Hacker News said

Recommends brightball · 2021-11 · on “Zig monthly, October 2021: Games, gamedev, Elixir, tools and more”

Really fascinating to see Zig being used to make Elixir cross platform! Exciting stuff. Here's a direct link to the ElixirConf talk: [this video]

Recommends kristoff_it · 2024-10 · on “Zigler: Zig NIFs in Elixir”

There's a series of things that a NIF must do to be a good citizen. Not crashing is a big one, but also not starving the VM by never yielding (in case the NIF is long-running) is important, plus a few secondary things like using the BEAM allocator so that tooling that monitors memory consumption can see resources consumed by the NIF. The creator of Zigler has a talk from ElixirConf 2021 on how he made Zig NIFs behave nicely: [this video]

Cites throwawaymaths · 2023-04 · on “The two types of C programmers (a provocative thesis)”

Got it. Thank you for your perspective. I can appreciate that comptime is tricky. Indeed, async zig is hard and annoying (but you're wrong about the function coloring... Here is someone's project where they call an async function alternately from a sync or async context with zero lines of code: [this video] Yielding is async and threaded is sync)

Cites h0l0cube · 2024-10 · on “Zigler: Zig NIFs in Elixir”

Links for anyone curious. > Syntax highlighting here can work correctly, actually. Highlighting shown here in the 2021 ElixirConf talk posted elsewhere in the comments: [this video] > I'm not sure why it's not better documented in Zigler Here's the docs for it (though buried in the 'advanced' section) [LINK]

Cites dnautics · 2025-07 · on “Zig breaking change – Initial Writergate”

something that I don't understand about the actual API: I maintain the zigler library, and one thing that was useful about the old async "colored-but-not-really" functions was that they implicitly tolerate having internal suspend points (detail: [this video] ) -- I'm not sure if having IO be a passed parameter will still let me do that? Can users build their own functions with yield points? And will you be able to jump out of the frame of a function and give control back to the executor, to let it resume later?

Cites dnautics · 2025-07 · on “Resizable structs in Zig”

RE: Elixir I have a feeling that the zig's i/o strategy will enable me to bring back the zig-async-dependent yielding nifs in zigler. I'm really hopeful io interface will have a yield() function, that would be even better! [this video]