Hum... Normally, when you start by calling `buildPath("path1", "path")` which mathces the variadic signature, but once you reach the body of the function, inside the argument becomes `["path1", "path"]`. By then, calling `buildPath(paths)` again should this time match the ranged version. That works on my release anyways, and it doesn't seem to be ambiguous.

Unless you meant ambiguous for the reader? I just found it strange to call a template with the parameter being the `typeof` it's only argument. Not that it is very important. I'll merge anyways.