metagn

> I know it's too late now to change this now, but some examples from the standard library of what I have in mind: Not really. [`securehash`](https://github.com/nim-lang/Nim/blob/devel/lib/deprecated/pure/securehash.nim) was moved to...

> Yes, it sucks big time because you have to disambiguate the "types.nim" filename every time you access the file. Module names should be unique for clarity and navigability. We...

Does `forbids` even work for exceptions? Also, I am uninformed about this discussion but if defects are so different from catchable exceptions (which you don't "catch", you "except") in their...

> Starting with your ideas as a Nimble package is a good development process. Not trying to plug but https://github.com/metagn/spread seems to do what is described here

It would be yet another feature but one could add double-backtick syntax to mean verbatim identifier. ```nim var ``__c``: int var ``a_a-12_f``: int var ``a:::b``: int var ``a::b``: int ```

Basically ```nim var ``a_a-12_f``: int ``` is equal to ```nim macro foo = let name = ident("a_a-12_f") result = quote do: var `name`: int foo() ``` This is how stropping...

Well, it shouldn't. The name `std/strings` is too broad, it's misleading if it doesn't export the infinite string stuff we have. Classifications like "miscellaneous string algorithms in the standard library",...

I thought the `sugar` part would be the obvious one. IMO it's better than putting all the random macros in the same module. We could maybe group them together, like...

There was a suggestion to use the reserved `[.` and `.]` for this purpose

I believe they are referring to Nim not having runtime effect handling, barring exception handling. Don't know what else is required in an effect system that could be missing.