← Back to context

Comment by jgalt212

1 day ago

I dunno. Depending on the writer and their particularly axe to grind the definition can vary widely. I would like it to mean, "any fixes I needed to make were minimal and not time intensive."

4 comments

jgalt212

Reply
overbring_labs  1 day ago

It's more of "yeah it worked, but I had to do a lot of hand-holding" and "it passes the tests but I cannot tell if the code has memory leaks".

Actually, I can tell; I ran split on the C source and got things like this:

disk_space.c:144:16: Only storage bin.ref_bin (type void *) derived from variable declared in this scope is not released (memory leak)

So I'm looking into a Rust version with Rustler now.

  • Zxian  16 hours ago

    I'd also recommend having a look at the Zig library for Elixir. For simple stuff, you can just inline, but support for pretty complex setups too.

    Also comes with a built-in BEAM allocator so the runtime properly reports NIF memory consumption.

    https://hexdocs.pm/zigler/Zig.html