`kill T` is not required, all we need to do is to turn `remove` into a
template, I think. But `kill T` is an interesting parameter passing mode, it's
interesting to think about it. It does **not** indicate that something is
fundamentally broken.
Thanks for all the replies guys.
Hello What is the state of events (aka callbacks, or signal/slot) Is there a
seamless "blessed" way of doing things -- a macro DSL which looks as part of
the syntax?
Thanks!
CP866 is usually used for console programs on Russian version of windows (which
is OEMCP), and CP1251 is usually used for gui programs on Russian version of
Windows (which is ACP). Technically I don't really see any reason why this
shouldn't be working with char types. However I would rather be
This is a already reported in this bug:
[https://github.com/nim-lang/Nim/issues/8015](https://github.com/nim-lang/Nim/issues/8015)
"Const arrays losing object variants data at runtime" though in my case it was
a proc field that was locked.
Seems like `enum` fields are also affected (and
Looks like this is a Nim bug. Normally you are not allowed to put an object
variant into a `const`. The compiler will error out if you do so. Apparantly
using an array somehow bypassed this check.
I think you should open an issue on
[nim-lang/Nim](https://github.com/nim-lang/Nim) for this.
