j
: Next unread message k
: Previous unread message j a
: Jump to all threads
j l
: Jump to MailingList overview
It's not safe. You need to protect concurrent access to all objects that are not specifically designed for thread-safety (like SharedQueues):
Actually SharedQueues protect themselves, or at least the code appears intent on doing so (it has its own 'accessProtect' Semaphore).
But yes, the standard "non-shared" classes like Set do not.
squeak-dev@lists.squeakfoundation.org