MetaLang

I'm not sure about this. On one hand, it's technically a breaking change because named `Tuple`s don't implicitly convert to un-named `Tuple`s: ``` void doSomethingWithFindResult(Tuple!(int[], size_t) t); doSomethingWithFindResult([ 1, 4,...

Hmm... you're right, but now I don't understand why. Maybe it's because they're structs that have the same layout, so the compiler allows them to implicitly convert to each other...?...

> what are the cases that break @andralex I'm surprised at what the compiler allows; these are the cases I could think of OTOH: ``` import std.typecons; Tuple!(int, "x", int,...

I'd suggest we leave uniting the overloads to a separate PR and get the fix merged.

If anyone can point out how I can add some tests for this case, please do so - it isn't immediately obvious.

> To mimick this behavior PATH should not be split simply by ; as done above the patch. This would also avoid the trouble with mismatched quotes in the report....