metagn

It seems like this never worked? Asking just to make sure what triggers it now Workaround is ```nim template unrecognizedFieldWarning = block: let value {.inject, used.} = 0 echo value...

Bisect gives #22716 I think it always silently errored, `typeof` just allowed it to be ambiguous before. If you try to run the code on the versions that work `typeof...

> and yeah, workaround works, but I can't say it makes sense at all, as a user at least ;) It is 100% a hack, ~~a more "proper" method would...

Never mind, there's a way simpler workaround lol ```nim import macros macro useIdent(name: static string): untyped = result = ident(name) template unrecognizedFieldWarning = trace "JSON field not recognized by the...

Just to be clear, I wasn't suggesting it as a permanent solution, the language design definitely needs to handle this. > a change in an unrelated module can have devastating...

I didn't think of this before but we can also make `typeof` accept the `None` type for now so the code still compiles if that'd help the situation. I was...

The problem is in `searchForProc`, it thinks it's redefining the other `parse` procs because it doesn't check if the generic params are different

With the potential design described in https://github.com/nim-lang/Nim/issues/22605#issuecomment-1710306313, each `foo` would become: ```nim Ident "foo0" OpenSymChoice Sym "foo1" {preferred} OpenSymChoice Sym "foo2" Sym "foo2" # neither preferred because name is ambiguous...

Doesn't need to be recursive, just needs to match a constraint again: ```nim type Comparable = concept proc `

Works in devel probably because of #23983