-
-
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
fatal.nim(54) sysFatal #21800
Comments
Another bug of similar kind, not possible to isolate. The hash of repo version to reproduce. Seems to be caused by distinct string type, when it's used where string is expected.
|
I'd suggest building a debug compiler and compiling the code, can atleast give more information than these error defects. |
Got similar bug today, build Nim from sources
|
It seems useful. |
Description
Got this error:
Unfortunately, I weren't able to create a small test case. I somehow fixed it, looking at the fix it seems like the error was caused by too much template nesting or something like that.
It could be reproduced by checking out the repo with this version d65b59f1083c71c509f418a488b7ce807aa34ba9
and running
nim r mono/examples/todo.nim
.Sorry for not providing the short example, this bug is very hard to isolate, feel free to close this issue if you feel like it's too much work to investigate.
Nim Version
nim -v
Nim Compiler Version 1.6.12 [MacOSX: amd64]
Compiled at 2023-03-10
Copyright (c) 2006-2023 by Andreas Rumpf
active boot switches: -d:release -d:nimUseLinenoise
Current Output
No response
Expected Output
No response
Possible Solution
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: