Timothee Cour

can you clarfiy? will the following work? ```nim type SortOrder* = enum k0, k1 proc sortOrder*() = discard proc foo*[T](a: int, sortOrder: SortOrder) = discard proc foo*[T](a: int, sortOrder: SortOrder,...

can `foo,int,SortOrder,T` introduce ambiguities? eg: ``` proc foo[T](a: int, b: SortOrder, c: T) proc foo[T](a: int, b: SortOrder[T]) ``` ## future work: * `osproc.nim#L1230` has: ```nim ## * `posix_utils.sendSignal(pid: Pid,...

> Is there any syntax expected for that? ya this should be discussed (but the preferred/encouraged way should be the simplest `See posix_utils.sendSignal_`) some options: ```nim # this should work...

> System.Text.RegularExpressions.Regex no need to go to extremes, but I do find @hlaaftana 's suggestion interesting. Heres's how it could work: * rule 1: every new module still under std/...

ya his talk is specific to C++ namespaces, his arguments don't really apply to nim which has different lookup rules (and doesn't rely on `include`); module path namespace (std/windows/wintypes vs...

>> The same way, adding a module in one library breaks imports in other libraries (which is why we've started to strictly avoid unqualified imports). > Agreed but mostly unrelated,...

>> the following is verbose and people avoid it because of that > [citation needed] personal experience + very crude stats: rg -t nim from lib | grep import |...

I mean on a technical level, wherever that linked PR ends (eg fusion or another nimble package)

* is there any workaround or it's really hard to fix? couldn't we merge issues by title which only differ by leading `Re:`* ? * who can I (as a...

I found this: https://www.mail-archive.com/[email protected]/msg63313.html ``` unfortunatily mailman is rewriting the Message-Id of > > the injected emails. > > > What Mailman version is this? This should not happen unless...