Range check error messages point to library code (point of check) rather than user code (point of error) about nelua-lang

[edubart]

This is not a bug, while compile time errors can traceback the origin of the error, runtime errors cannot. Runtime asserts and checks will only show the line where the error happened.

There is no good cross platform and lightweight way to perform tracebacks at runtime, the best you can do is to use --sanitize (available only in some systems) so it gives a C traceback of the error. Luckily the C function names are not that hard to understand, and even the C code is not hard to follow when debugging nasty bugs.

I see this as a possible enhancement for the future, that is, to have nice tracebacks messages in case of runtime errors, showing Nelua code, not C code. But it's not that simple to do, and the cross platform way would pollute the C codegen with frame tracing everywhere and also hit performance, I would have to introduce a debug build.