metagn

Maybe we can move the modules in fusion to their separate repos then make fusion a nimble package that depends on all of them. i.e. ```nim # fusion.nimble requires "matching"...

I think modules will have activity as long as people use them. The issue with fusion seems to be largely with visibiliity, or people just don't know how to install...

The idea of fusion might not have been executed well but I agree the modules in it are definitely worth preserving with at least the same degree of respect as...

> The main issue with fusion is that there is no maintainer, nobody cares about it, so splitting it will just rearrange the problem a bit differently Splitting it allows...

> Fwiw I use fusion/astdsl all the time and there is nothing I wish to be added or fixed, it's just done. This is the case for a lot of...

Working implementation of the described solution in the RFC as reference for future/just in case https://github.com/nim-lang/Nim/pull/21673

Ok well if we aren't implementing this we should at least document this limitation along with the workaround as outlined [here](https://github.com/nim-lang/Nim/issues/20274#issuecomment-1518222024).

To resolve overloads, each argument in a call expression is iterated over, and if the argument type for an overload at some position is not `untyped`, that argument in the...

> it's subtle for newcomers I've been looking up operator precedences from the manual since day 1 of using Nim (really any language). With this logic precedence is bad too...

That's not necessarily the only use of this. I usually hesitate to make posts like this because you have to mention examples and if you don't mention enough, the specific...