metagn

It's just a placeholder, didn't want to use alias to not conflate with the other alias proposed feature, but now that I think of it `symbol` is much more confusing....

For forcing a template reference, I considered unary `&` in consistency with Ruby/Crystal and D defined as a magic in system, I think no one uses that. If they do,...

> things quickly get complicated when you pass the template to a regular function and you need a run-time representation of the template We don't need a runtime representation. The...

I hacked this together: https://github.com/hlaaftana/applicates This library creates the template when it's called (using a cache which I'm not proud of. are macro caches good practice?), not where it's defined....

While writing tests for my package I came up with something that would be translated into the syntax in this proposal like: ```nim template iter(iter: untyped): untyped = template(agg: template):...

IMO `fill`/`product`/maybe ` reverse`/`rotate` should be in `sequtils`, the rest should be in a module `std/sort` or `std/ordering`. `import algorithms` is not much better than `import algorithm`

I think the naming convention is good but "algorithms" is so vague it loops back around to making no sense for the module. At the risk of sounding repetitive a...

Funny hack ```nim proc plusExists[T]: bool = type Foo = concept proc `+`(x, y: T): T result = void is Foo echo plusExists[int]() echo plusExists[string]() ```

For json just use `%`. ```nim proc toJsonNode[T](val: T): JsonNode = %val ``` I wouldn't know about how necessary rewriting the newLit procs is, but if you want a nnk...

About `-pkg`, there is supposedly [`--package`](https://github.com/nim-lang/nimble#nimble-run) but it's only documented under "nimble run".