Skip to content

Fix script issues caused by the class wrapper #2247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MaciejG604 opened this issue Jun 27, 2023 · 0 comments
Open

Fix script issues caused by the class wrapper #2247

MaciejG604 opened this issue Jun 27, 2023 · 0 comments
Labels
bug Something isn't working script-wrapper

Comments

@MaciejG604
Copy link
Contributor

MaciejG604 commented Jun 27, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working script-wrapper
Projects
None yet
Development

No branches or pull requests

1 participant