-
Notifications
You must be signed in to change notification settings - Fork 52
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
failing on windows? #21
Comments
Sorry but this is not Chronos bug, but new bug of Nim compiler. This function do not touch any global values which are in GC memory. Until @Araq will not explain new |
@cheatfate, the issue is that the code makes a call through a function pointer, which is not marked with nim-chronos/chronos/asyncloop.nim Line 243 in 9f15c6b
Since the pointer is not |
Based on Nim appveyor tests, this package fails on Windows.
I don't have Windows so I cannot reproduce, but I have been told that running
nim c tests/teststream.nim
produces..\chronos\transports\stream.nim(287, 27) Error: 'writeStreamLoop' is not GC-safe as it performs an indirect call here
/This is likely connected to nim-lang/Nim@c86b1fb and could probably be fixed on your end by some extra
{.gcsafe.}
at some places.The text was updated successfully, but these errors were encountered: