-
Notifications
You must be signed in to change notification settings - Fork 0
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
Build fails when using --gc:arc. #17
Comments
This seems like a nimterop bug, I'll try to reproduce this and talk about this to @genotrance. Meanwhile, make sure that you're running latest nimterop and regex, they have caused some problems for me on devel. (oops, closed accidentally) |
Unfortunately nimterop does not have ARC support yet, you'll have to use a different GC for the time being. |
Alright. Thanks for checking into this. Here's hoping they can get that fixed up soon! |
This isn't a nimterop issue. If you compile just There's something in
|
@genotrance, right. I already encountered at least two more issues where euwren triggered some edge case in the compiler in the past, I may be able to debug this myself somehow. Unfortunately I wasn't able to report them properly since I wasn't able to reproduce them in a minimal example. |
Hi! Sorry if this bug report doesn't follow any predefined template or guidelines as I didn't notice any info on one. Nim just updated the other day and moved the new arc GC to stable, so I am currently trying to prep a prototype in-house game engine tinker project to take advantage of it, which uses euwren for the scripting layer. Unfortunately, the build fails with:
If I build with the default garbage collector or remove euwren and use arc, there appears to be no problem, so I'm fairly certain this isn't on my end (though if it is I do apologize for taking up your time). I don't mean to rush you or anything since this update just dropped (as of this report) yesterday, and frankly I can just disable that component on my end for now. I just wanted to make sure you were aware of the issue 😄
The text was updated successfully, but these errors were encountered: