Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
ams6110
on Nov 26, 2017
|
parent
|
context
|
favorite
| on:
Carp, a compiled Lisp with type inference and a bo...
It actually makes reasoning easy. What gets copied: everything. What gets shared: nothing.
im_down_w_otp
on Nov 26, 2017
|
next
[–]
Except that isn't true in Erlang (or other BEAM languages). Binaries larger than some threshold are managed on a shared-heap. I think a couple other things have been promoted to being managed that way too fairly recently.
ramchip
on Nov 26, 2017
|
parent
|
next
[–]
You might be thinking of the optimization for constant pool references:
https://medium.com/@jlouis666/an-erlang-otp-20-0-optimizatio...
im_down_w_otp
on Nov 26, 2017
|
root
|
parent
|
next
[–]
Yes, that. Thank you.
banachtarski
on Nov 26, 2017
|
prev
[–]
That's not true in a number of cases, and thankfully what you said isn't right or the BEAM would truly be a disaster.
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search:
