Clay Sweetser

@Araq > There is considerable overlap with my unwritten RFC "nullary non-overloaded templates should be resolved early and allow for aliasing of the template body". **Can we unify aliases and...

With regards to *general* standard library code, I think the default should be oriented towards security (e.g., external input shouldn't be able to crash a server implementation). With regards to...

> When writing or using security sensitive code, you should read documentation This also assumes that the documentation is in a language you can read (or read well enough to...

> Edit: wait.... hear me out here... BLOB LION... with a crown!?!!? Or blob honeybadger (though, I still like @rigani's mascot, if we're going for "cute")

As far as syntax goes, why not simply reuse the `varargs` metatype? It's not as if a generic parameter list is actually restricted to typedesc arguments (see array constructors).

@Araq but there are still things like matrices and other areas that would benefit from variadic generic types.

> I believe centralized package registry should be optional Yes please. Speaking from experience with Python, requiring a central repository makes using package management in the private space a headache,...

@Araq How does it weaken type safety?

As a compromise, what if this only applied to string literals? ```nim func `/`(head: Path, tail: Path | string{lit}): Path {.inline.} = joinPath(head.string, tail.string).Path ``` This allows the convenience of...

> Isn't `Path("/foo" / "bar" / "baz")` valid as well? Why would it be, if `string` (or `static[string]`) doesn't have a `/` operator?