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
The class script wrapper that has been introduced in v1.0.0 (#2033) as a remedy to thread deadlocks, has proven to be quite problematic. E.g. #2128, #2157, #2241
The issues arise usually when the user-defined classes get passed as types.
A next-step would be to introduce a more complex script wrapping that allows for placing all user's class definitions outside of the wrapper class.
Solution until the above is fixed
A viable solution is to fallback to the old type of wrapper, this is done with --object-wrapper command line option or with //>using objectWrapper directive.
With the object wrapper caution secondary threads should be avoided, though sometimes it's possible to work around this by using another level of encapsulation - see #532.
The text was updated successfully, but these errors were encountered:
Version(s)
v1.0.0 and newer
Describe what needs to be done and why
The class script wrapper that has been introduced in v1.0.0 (#2033) as a remedy to thread deadlocks, has proven to be quite problematic. E.g. #2128, #2157, #2241
The issues arise usually when the user-defined classes get passed as types.
A next-step would be to introduce a more complex script wrapping that allows for placing all user's class definitions outside of the wrapper class.
Solution until the above is fixed
A viable solution is to fallback to the old type of wrapper, this is done with
--object-wrapper
command line option or with//>using objectWrapper
directive.With the object wrapper caution secondary threads should be avoided, though sometimes it's possible to work around this by using another level of encapsulation - see #532.
The text was updated successfully, but these errors were encountered: