Re:Comparing Elixir and Go
by lobster_johnson on Friday January 27, 2017 @01:42PM
(#13501615)
Erlang is purely immutable and doesn't have any "facilities for mutation" that I know about, although it does have side effects (I/O, but no Haskell-style effect system).
Re:Comparing Elixir and Go
by im_down_w_otp on Saturday January 28, 2017 @08:15PM
(#13511011)
That's not entirely true. I built a FlatBuffers implementation for Erlang as NIFs so that I could still take advantage of FlatBuffers memory efficiency features, which fundamentally required "unsafe" and mutable access to a byte buffer. I just had to be very aware of exactly how the runtime was going to interact with my implementation and account for it.
Sadly the place where I worked was not keen on open source posture, so it's locked away for all of time probably. However, the place I now work is a lot more open source friendly and I expect to take another whack at it, but using Rust on the NIF side this time around instead of C.
Re:Comparing Elixir and Go
by lobster_johnson on Monday January 30, 2017 @04:49PM
(#13525359)
Well, with NIFs you can do anything — it's a parallel C universe. I was really referring to Erlang the language.
So where does the myth that you can't exit out of immutability come from?