konsumlamm

Rust also has this shorthand syntax and I'm not aware of any problems with it.

> This seems to just be a workaround version of "Object constructors should infer the type". There is no reason one needs to specify default specialization if the following is...

> > This feature would still be useful to save some typing in the common case where the type parameter is the default type > > Is this really a...

> Interfaces can almost be implemented with `concept` but there are several issues: > > * `varargs` don't like concepts > * `@[x, y]` don't detect the common concept These...

> If we need `type Animal = vtref CAnimal` to transform the concept as the type, then why currently, the following code is working: > > ```nim > assert(Human is...

Since this hasn't been mentioned yet, some prior art (in order of relevance for Nim): * Go has interfaces, which can be used as constraints for generics, but can also...

> @konsumlamm Let's say we have `type VAnimal = vtype CAnimal`, what will be the difference between `proc interact(animal: CAnimal)` and `proc interact(animal: VAnimal)`? `CAnimal` is implicitly used as a...

`std/atomics` and `threading/atomics` look very similar, but there are some differences: * `std` has an annoying `mo` prefix for memory orderings * `std` also supports non-trivial types, which is a...

> There was a plan to add DSL to allow users to construct help message if default one isn't suitable. Is this still planned?

> The reason it was done this way is that you can easily introduce a new scope via `block` on your own, but you cannot easily remove it when the...