3 ms·
I'd have to think about this more, but I think your purported solution (mostly immutable record-type objects) would tax performance and memory constraints.
by dvt 7y ago
I'd have to think about this more, but I think your purported solution (mostly immutable record-type objects) would tax performance and memory constraints.
- lmm 7y agoHaskell already works that way, and is a high-performance language. (The same is true of strict ML-family languages, so laziness is not required to make this practical). Those languages generally just don't bother with reference comparisons at all, but one could imagine a more hybrid language that included support for traditional OO - in fact idiomatic Scala works like this (and again is a high-performance language, though to some extent that relies on what's probably the best garbage collector in the world). I don't know what kind of support Erlang has for making comparisons between actor identities, but that might be an even better example.