Timothee Cour

I'm looking for the best possible approach to have D-like range behavior (cf https://github.com/alehander42/zero-functional/issues/21 for related packages), so I was trying to evaluate yours. Also I'm experimenting with a design...

* nimsuggest does't work if it's compiled somewhere else than default location eg: this won't work ``` $nimc_D/bin/nim c -o:/tmp/nimsuggest_dbg --noNimblePath -p:compiler --debugger:native nimsuggest/nimsuggest.nim ``` after running nimsuggest you'll get:...

> Your proposal make sense but I think untyped parameters are an anti-feature and should be phased out entirely i disagree but this should be discussed in its own dedicated...

* issue closed but not clear it was addressed: https://github.com/nim-lang/nimsuggest/issues/64#issuecomment-435481945 * likewise with https://github.com/nim-lang/nimsuggest/issues/38#issuecomment-435482237

I don't think https://github.com/nim-lang/Nim/pull/18618 is the right fix; it doesn't help with this important case: optional params with a block trailing param, a very common pitfall that requires annoying workarounds...

> @timotheecour I have an idea. I like it! can you open a separate PR for this? (you can leave the other PR open in the meantime); I expect this...

> Making default arguments work with untyped bodies sounds like it should be part of a completely seperate RFC. here you go: https://github.com/nim-lang/RFCs/issues/405 > Possibly combined with named only arguments...

> Does it need to be magic? I don't see how that could work without relying on a `{.magic.}`? > Or can we lift something already implemented in sigmatch? yes,...

why would it be more efficient? `=default` is `{.compileTime.}` and affect semantics of `var` initializaiton, so that: ```nim var a: Bar # a is not zero-initialized, it's directly initialized to...

@Araq > I prefer a langauge with a low barrier to entry though. A standard library does not have to be a strange beast that uses every feature the language...