Esteban C Borsani
Esteban C Borsani
this does not work on Windows. This one does https://gist.github.com/nitely/db7ada4b3d63bd77f15cda4f7fe2f37e
@Graveflo I think this injecting the stack trace into the msg is from before "reraised from" existed and it should be removed. Unless there is something I'm missing there is...
@Graveflo Before I added that filtering [here](https://github.com/nim-lang/Nim/pull/24563) it used to just contain the top traceback. There was no point to it afaik. I guess it's nice that it shows the...
Issues: - `libbacktrace` tests: the stack trace contains "unitest2.nim" file lines that point to `PreMain, PreMainInner, main` internal Nim functions for whatever reason. If we just run testasyncstacktrace directly those...
I was expecting the constrained generic to match the same as the concrete type proc version, as it seems to be the case for every other type. It also seems...
Another overload regression in 2.0.16: ```nim type FBase {.inheritable, pure.} = object type FA = object of FBase type Obj[T] = object proc foo[U: SomeFloat](s: Obj[FA], x: U) = echo...
This can occur when closing the socket while sending or receiving, because `socket.sslHandle` is freed. The sigsegv can also occur on calls that require `socket.bioIn` or `socket.bioOut` because those use...
You can check if #24795 fixes this.