PooledArray is potentially not thread safe about pooledarrays.jl HOT 1 CLOSED

Like in CategoricalArrays, the problem is that even if we took a lock on each setindex! call, calling getindex in parallel wouldn't be thread-safe if a new level is added (as the pool may be resized). Yet taking a lock on getindex would kill performance.

Also, taking a lock on each setindex! call would make it impossible to run it in parallel, yet that's perfectly safe if you know that you don't add many levels. Not sure whether it's a typical case or not, but that happens e.g. if you reorder values in the array (e.g. sorting).

What we can do without affecting performance is take a lock when adding new levels. That should at least fix the example you give, and adding levels is relatively slow and can't be done in parallel anyway. But that doesn't provide a lot of safety either.

from pooledarrays.jl.