Illegal storage access

Actually, I misunderstood the docs. Importing the segfaults module allows you to catch a segfault like you would an exception. So you could do: import segfaults proc main() = try: doSegfault() except: echo "segfault caught!" echo getCurre

Illegal storage access

Yesterday I also had a compilation message with version 1.6.6 it could no longer compile even a small example. I reloaded 1.6.4 everything worked perfectly. I deleted 1.6.6 then reloaded everything is back to normal. etc... I had reported the issue, but deleted it thinking it was mine.

How to determine why shared lib is linked

Changing that did remove the link but my apk just crashes now when trying to load the .so

Illegal storage access

import segfaults Run added to his main.nim source text can catch a compiler issue? I am surprised, but your reply got two likes, so it may indeed be true. > > On compilation, I get only this message. For debugging the compiler, I found this:

Illegal storage access

You can try using import segfaults Run In your main nim file. It might be able to give you a traceback.

Illegal storage access

Why are you running a 32-bit version of the compiler? Does this happen for a very minimal program, e.g. echo "hello world"? If not, try commenting out code in your program until you've narrowed down which line is causing the compiler to crash, and post that line here.

Nim packages dependencies visualizations

If there is interest for this I could add and direct dependency listing to I'm concerned about the increasing fragmentation of dependencies in the Nim ecosystem leading to low stability and high churn. Would people be interested in a dependency health gauge to be dis

Ctrie in Nim for concurrent iterators?

Controversial opinion ahead: All this lockfree stuff is so severely limited and error-prone and hard to reason about that it's to be avoided at almost all costs. For example: Serial code like `tab[k] = tab.len # map k to unique ID` is not correct in a multi-threaded setting just because you swi

could javascript backend make use of new javascript ES6 module support?

I would find support for ES6 modules also very interesting, so that I can use nim to create ES6 modules, basically letting a nim package correspond to a module. Treating JavaScript like WebAssembly doesn't make too much sense, in my opinion: Why not compile just to WebAssembly then, if you are n

Illegal storage access

If it happens when you try to compile, thats a bug in compiler. If you can share your code maybe somebody would help to locate the bug or you may try to compile compiler in debug mode to see where it crashes.

Nim packages dependencies visualizations

Nice! As maintainers of lots of Nim packages, for us it's also often interesting to know the reverse dependencies - ie given a package like chronos, what depends on it?

Nim packages dependencies visualizations

Looks very cool! Have you thought about sharing recursive dependencies instead of duplicating them? eg for amysql, unicodedb is a dependency of segmentation, unicodeplus and regex, so it's shown 3 times instead of 1 time with 3 links The graph may look a bit messier, but may be more representat

Carbon lang

> Was this pinned by mistake? Yes, I misclicked somewhere. :-)

Illegal storage access

> nim c main.nim SIGSEGV: Illegal storage access. (Attempt to read from nil?) Run On compilation, I get only this _message_. How can I find the **source of error** (Illegal storage access) in my code? Compiler Details Nim Compiler Version 1.6.6 [Windows: