3 ms·
There's also Zigler, that makes writing NIFs in Zig a breeze: https://github.com/E-xyza/zigler https://github.com/E-xyza/zigler
by jedisct1 3y ago
There's also Zigler, that makes writing NIFs in Zig a breeze: https://github.com/E-xyza/zigler https://github.com/E-xyza/zigler
- veber-alex 3y agoI am confused by the examples, do you actually need to write your code as a text string?
- cassepipe 3y agoWell it seems that those are two different approaches. Rustler being a Rust library to write Rust NIFs for Elixir. So I guess you have to compile the NIF first and then use it. On the other hand Zigler seems to be an Elixir library that you give a string of zig code and it probably offloads compilation to the zig compiler. Since Elixir is compiled to bytecode, if you don't modify it won't get unecessary recompiled I guess so the approach has merit I think. Btw it's a sigil'ed string, that is the result of a function that takes a string and returns one rather than a string literal
- alberth 3y agoThis is way less safe than Rust. NIFs have a major downside in that it can take down the entire BEAM if they misbehave. And a huge reason why people use Erlang, is its resiliency from outages. With Rust memory protection, it gives people more confidence in using NIFs for exactly that reason.