You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is a bug or a known limitation. The generated code is not thread safe. I understand that with Tcl's thread/interp model, a speedtable cannot be accessed from multiple threads. However, because of the use of static caches (e.g. for allocation of rows), it is not safe to even access different speedtables from different threads.
Docs don't talk about this much
/Ashok
The text was updated successfully, but these errors were encountered:
It probably makes sense to do this as one of the goals of the new cpp branch. Some of my work there was to begin looking at how the static global speedtablesAssocData was being used, though I didn't make any major changes to it yet.
Not sure if this is a bug or a known limitation. The generated code is not thread safe. I understand that with Tcl's thread/interp model, a speedtable cannot be accessed from multiple threads. However, because of the use of static caches (e.g. for allocation of rows), it is not safe to even access different speedtables from different threads.
Docs don't talk about this much
/Ashok
The text was updated successfully, but these errors were encountered: