shootout - nsieve-bits benchmark

Kostis Sagonas <>
Mon Apr 24 11:13:39 CEST 2006


 > Well, that seems handy (esp. in a compiler). The array
 > update function seemed to be destructive though? 

Yes.

 > So I guess my question is: do these arrays behave like
 > ets tables or like terms? For example, what happens if
 > array A is sent from P to Q, then updated in P -- will
 > Q see the update? 

For most uses (i.e., when the array is big enough) the
binary is stored off-heap, so for practical purposes the
answer is "yes".  But this has not been our concern in
uses so far.

Kostis




More information about the erlang-questions mailing list