IndexError: list index out of range

An index in [Python](http://net-informations.com/python/iq/default.htm) refers to a position within an ordered list . This error basically means you are trying to access a value at a List index which is out of bounds i.e greater than the last index of the list or less than the least index in the

Survey Question: flow research

Maybe there isn't much documentation beyond the examples included in the docs, but there are plenty of easily found examples on github if you know how to search on github effectively. If not I highly suggest you learn to use github's code search features. It's basically how I learned to program

Survey Question: flow research

> Perhaps the point that makes me most sad is the little evolution I noticed in > the asynchronous modules. Since I met Nim until today, I see such information > in the asyncdispatch package: "The async procedures also offer limited > support for the try statementUnfortunately the semantics

Dynlib passing value back to main app causes SIGSEGV error

Thank you. I'll be using it if that's the way to go.

Dynlib passing value back to main app causes SIGSEGV error

Thanks a lot. I'll take a look at the resources you linked to.

Survey Question: flow research

There many issues that I believe Nim still needs to address before it can truly be a success story. It is already an impressive and inspiring one, but long term success cannot be claimed until we arrive at a future point in time. It's TBD but I think these things are hurting Nim's chances of ful

Did you know that Nim has had enum-indexed arrays since 0.18? Poll Inside!

I did not know it was since 0.18, I thought it was much older.

nlvm update - llvm 13.0.0

> updated c2nim used to generate llvm bindings - it regressed since the last > time I used it and no longer parses several enums and typedefs used in the > llvm headers - on the plus side, it no longer stops on errors Please report these regressions ... eventually. :-)

Did you know that Nim has had enum-indexed arrays since 0.18? Poll Inside!

> It appears it might have initially been a bug that became a feature - as it > partially worked in 0.13 and then has worked fully since 0.18. It always has been planned as a feature as this was taken from my list of "things that Delphi got right". However, I am not so sure anymore this feature

Did you know that Nim has had enum-indexed arrays since 0.18? Poll Inside!

It'd be sweet if whatever forum software the Nim community used, just had surveys :)

Did you know that Nim has had enum-indexed arrays since 0.18? Poll Inside!

Yes, it does have a sentence in the manual about it, but it is unknown to a lot of folks I think... I think it was brought up in a nim developers meeting stream at one point, but I think a lot of folks may not know about this! It's really quite a cool feature and this thread is more of an attemp

nlvm update - llvm 13.0.0

`nlvm` just got a little refresher and is now based on `llvm` 13.0.0 - mostly a trivial update from the point of view of `nlvm` as llvm turns out to have quite a stable API: * updated c2nim used to generate `llvm` bindings - it regressed since the last time I used it and no longer parses seve

Did you know that Nim has had enum-indexed arrays since 0.18? Poll Inside!

It's not really a secret feature - you can use any ordinal type to index arrays, and enums are ordinal types too.

Did you know that Nim has had enum-indexed arrays since 0.18? Poll Inside!

Just a tip for organizing non-exclusive surveys: we have likes, so you could have a few replies below the post with options which people can like. Same works for GH.

Did you know that Nim has had enum-indexed arrays since 0.18? Poll Inside!

I apologize for having to include a link to a website like `poll-maker.com` but nim-forum doesn't allow embedding HTML and lacks a poll feature, so I have to resort to stone age hyperlinks. Is what the poll looks like, so you don't have to waste

Survey Question: flow research

The more C/C++ you know the better armed you will be to tackle the interop situation. It isn't well documented, because if someone don't understand how a C/C++ compiler and linker work, it is difficult to explain how to effectively use the interop feature set to them. This is why projects like f

Dynlib passing value back to main app causes SIGSEGV error

`--gc:orc/arc -d:useMalloc` is highly recommended for DLLs these days.

Dynlib passing value back to main app causes SIGSEGV error

You really need to understand what you're doing if you're going to be moving GC'd memory across DLL boundaries like this. You have to know when to `GC_ref` and `GC_unref` because otherwise memory you try to access might already have been collected by the GC - that or you'll cause leaks by not de

Is something like EnTT possible with Nim?

Makes sense. It’s cool that you are publishing it though.