Managing mutable data in Elixir with Rust
lambdafunctions.com
Managing mutable data in Elixir with Rust
1–10 of 61 posts
Re: Managing mutable data in Elixir with Rust
#2Getting rustler up and running for us was very easy. Thank you to the team for making this excellent library.
We had some inconsistent build results (ours is an umbrella app) but apart from forcing a compilation and losing the ability to cache the rust builds, everything else has worked so well so we’re happy to get access to the massive rust ecosystem.
Re: Managing mutable data in Elixir with Rust
#3It’s exactly this use case that nudged me (primarily an Elixir dev) to start learning Rust a few years back.
Unfortunately, I haven’t had a project where I’ve needed to use Rustler yet, though.
Re: Managing mutable data in Elixir with Rust
#4Cool writeup. A little ironic, since Erlang's `digraphs` are also mutable!
Re: Managing mutable data in Elixir with Rust
#5Nice. I thought that Zig would be a nice language for writing NIFs - but of course Rust would be good too. Cool!
Re: Managing mutable data in Elixir with Rust
#6Cool writeup. A little ironic, since Erlang's `digraphs` are also mutable!
Erlang's digraphs are stored in an ETS table, so aren't they only mutable in the same way that ETS tables are mutable?
I don't normally see people consider (D)ETS tables as mutable, however.
Re: Managing mutable data in Elixir with Rust
#7Nice. I thought that Zig would be a nice language for writing NIFs - but of course Rust would be good too. Cool!
Zigler! https://github.com/E-xyza/zigler
Re: Managing mutable data in Elixir with Rust
#8Nice. I thought that Zig would be a nice language for writing NIFs - but of course Rust would be good too. Cool!
[deleted]
Re: Managing mutable data in Elixir with Rust
#9Cool writeup. A little ironic, since Erlang's `digraphs` are also mutable!
Erlang's digraphs are stored in an ETS table, so aren't they only mutable in the same way that ETS tables are mutable? I don't normally see people consider (D)ETS tables as mutable, however.
Yeah. I think even though the article doesn’t use it as an example, what’s really desirable about escape hatching to a systems language is the ability to in-place mutate lots of data. Specifically sparse mutations of a large chunk of data where a copy penalty would be wasteful. ETS is basically just swapping pointers (which I hope is mutation under the hood)
Re: Managing mutable data in Elixir with Rust
#10Immutable data is not a “foundation of scalability and robustness”.