zah

I would further argue that this helper is present in most async run-times. Here is the JavaScript version for example: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/any

Here is `race` in JavaScript: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/race

I'll try to summarize my position here. At the moment, the support in the compiler for explicit generic params is very much incomplete and requires quite a lot of work...

@hlaaftana, the typedesc params are still a compile-time mechanism. When it comes to code generation, they behave exactly as regular generic params (the proc gets instantiated for each unique type).

If we want to have consistent libraries, we must deprecate one of the mechanisms. Otherwise, people will always choose the mechanism they like more and this thread have demonstrated that...

> the stdlib heavily leans towards [T]. @Araq, my point expressed in some of the linked discussions is that this bias in the standard library is leading people to using...

@Araq keeps claiming that my original attempt to solve the cyclic dependencies problem through the `noforward` pragma is not compatible with the effects system, but I've never seen a compelling...

This issue have two parts: 1) Supporting the definitions of generic types such as TVariant that may depend on a list of types supplied as a parameter. 2) Supporting procs...

This is an interesting proposal, but I don't think it will work out with regular type aliases. Nim has a lot of internal code that tries to eliminate the intermediate...

There seems to be a misunderstanding here. The `depfile` needs to show a list of files that Nim read during the compilation process, not the list of compiled C sources....