Timothee Cour

> If the compiler needs big integers, shouldn't it finally start to use Nimble packages? I agree; what this would require is: * locking down all recursive dependencies to avoid...

@zah since you brought this up can you please create either an issue or RFC so it can be discussed exclusively and separately in a dedicated location instead of here...

## proposal `mini-gmp` (subset of https://gmplib.org/) could be a good candidate to port/wrap: * single header, single source, no dependency * API-compatible with gmp so users could link against `-lgmp`...

@niekbouman judging from https://github.com/niekbouman/ctbignum/issues/39 > With ctbignum, I am focusing on compile-time computations and run-time computations with integers whose limb size are known at compile time, and modular arithmetic with...

I support the idea of colorful error messages, but I'm not sure this is the right approach, because it pollutes compiler sources with formatting, in potentially lots of places. D's...

@beef331 now that your other https://github.com/nim-lang/Nim/pull/18384 was merged, any interest in continuing this? I still prefer this approach to https://github.com/nim-lang/Nim/pull/16446, because it's simpler, and is also simpler for code that...

great. Note also that for this PR, you don't need to cover all cases, IIRC what you had was already close to mergeable, it can always improve in future work;...

what I have in mind is actually a small change, not a big change: replacing network calls like: ```nim var (output, exitCode) = doCmdEx("git ls-remote --tags " & url.quoteShell()) if...

ok i see; looks like every package I tried have `nimble path` pointing to dir where the nimble file is, not where the base of the import is, eg: nimble...

at very least for debugging, to figure out which file was selected by nimble (eg in case there are multiple versions of the same packages); eg if you've installed X...