Timothee Cour

[40200 – color prompt causes wrong indentation of cmds (with `settings set prompt "\033[31m(lldb)\033[0m "`)](https://bugs.llvm.org/show_bug.cgi?id=40200)

not just windows: OSX also please update docs until this is fixed? (ie, link to this bug below `rdmd --build-only digger`)

* with today's compiler, we can't use `Iterable` concept for something that accepts an iterator such as `toSeq(myIter(3))`, see https://github.com/nim-lang/Nim/issues/8774#issuecomment-415993902 I have an idea for how to fix this (in...

* object seems better than tuple (for the exact reason you mentioned + other reasons) * instead of breaking code, how about deprecating walkGlobKinds (via `{.deprecated: "use walkGlobEntries".}`) and adding...

Noindex should work, see https://developers.google.com/search/reference/robots_meta_tag

so your solution when a program (eg, nim itself) compiled with --stacktrace:on is too slow is to: * find all the bottlenecks (that's really hard, it depends on use cases,...

well I've updated https://github.com/nim-lang/Nim/pull/13582 so that existing semantics are unchanged, instead the new --stacktrace:noinline can give you large speedups while typically producing identical stracktrace, ie, a good compromise bw speed...

> I'd be happier with templates instead of inline procs as inline procs are currently not inlined in debug builds (from https://github.com/nim-lang/Nim/pull/13536#issuecomment-593911621) > All that's really needed IMHO is that...

> It's not about speed really, .inline should inline. If it results in slower code than we misapplied the .inline pragma. It's about being more predictable. this would be bad...

> There are no other reasons for inline's existance yes there is a very important one: it tells the compiler that, when crossing module boundaries, the foreign function may be...