-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Migration to v2 #20017
Labels
Comments
ringabout
changed the title
[meta] important pacakes which doesn't work with arc/orc and reasons
Migration to ARC/ORC
Jul 25, 2022
Merged
Hey, is this the right place to report that programs using nimPNG don't compile on devel? shallowCopy usage: |
I think you probably need to open an issue on the issue track of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cannot cast ref to RootRef in Arc/Orc
affected important packages:
Solution
shallowCopy/shallow
Solution
shallowCopy
/shallow
becomes a compile-time error with ARC/ORC.move
seqs/strings instead.You can also use
sink
to let the compiler decide whether to move the data or copy the data.Another solution is to use
{.cursor.}
.deepcopy
Solution
Enable deepcopy for ARC/ORC. Use
--deepcopy:on
. Note that the option appears since 1.4.0 and it is ignored with refc.cannot bind another destructor to ref object
#19231
affected important packages:
minimal testcase
{.global.} pragma doesn't work when the variable is initialized with non-value types
#17552
Solution
None
threadpool doesn't work with ORC
Solution
Switch to https://github.com/status-im/nim-taskpools or use createThreads.
Mixing declarations and statements at the top level causes undefined behaviour
#19795
affected important packages:
Solution
None.
Workaround: move the top level statements to the main procs.
defaults to ORC
#19972
stricteffects
experimental:stricteffects
is enabled for v2. There is a switch--legacy:laxeffects
to keep backwards compatibility with old behaviors.ref #19303
ref nim-lang/RFCs#435
The text was updated successfully, but these errors were encountered: