revert volatile mod from values RubyArray store? #5348
maybe I am missing smt but from reviewing parts doesn't bring much value
from the commit desc that introduced it ... seems to be due nil fills after assignment, makes no sense?
... but only
I approve. RubyArray may deserve some proper volatility checks in the future but this partial change was not really sufficient to make sure the new state of the array is properly visible. It also adds volatile write overhead to every (already not thread-safe) update of the RubyArray values store.