Clyybber

Maybe we should add an `unmaintained` or `deprecated` in such cases?

Specifying `rasises: []` on a proc should also get rid of the branching introduced by `exceptions:goto` when calling that proc.

Yeah, if you specify `raises: []` then the compiler will see that it can't raise, and thus won't introduce branching (with `--panics:on` that is).

@timotheecour > a destructor can't deallocate stack allocated memory, so stack allocated memory can't be invalidated even if a destructor is called. If you disagree please provide an example. The...

tyRef also uses destructors in gc:arc, and destructors can be used to implement custom ref types. Those would be tyObject.

Your example relies on the fact that seqs can't be nil. Replace the seq with a ref or a ptr. It will crash. Escape analysis must take the destructor scope...

It's not memory safe. Keep in mind you don't know what the destructor will do with the pointer/ref; destructors do not have to reset their target anymore.

``` wanted X gotten Y ``` could also work, but I don't know how it sounds to native english speakers :D

@cooldome We can already do `array[SomeEnum, T]`; it makes sense if you think of enums as a set of their valid entries. But then you could also say it makes...

This does not actually fix https://github.com/nim-lang/Nim/issues/11225 from what I can tell.