No we shouldn&#x27;t. I would even go further and would say if it&#x27;s accessed from a different thread it should better fail immediatly with a hard error that everybody can see.<p>Multithreading isn&#x27;t something that should be implicit. Either you design your whole module&#x2F;library&#x2F;application around to be used from multiple threads (with all the extra work for synchronization and typically also well defined thread boundaries) or you stay with single threading.