observation: D getting a bit complex

[BBasile via Digitalmars-d-learn]

On Sunday, 30 August 2015 at 10:42:24 UTC, Spacen Jasset wrote:
> On Sunday, 30 August 2015 at 07:36:55 UTC, BBasile wrote:
>> On Sunday, 30 August 2015 at 02:42:30 UTC, Spacen Jasset wrote:
>>> immutable(ElementEncodingType!(ElementType!Range))[] 
>>> buildPath(Range)(Range segments) if (isInputRange!Range && 
>>> isSomeString!(ElementType!Range));
>>> pure nothrow @safe immutable(C)[] buildPath(C)(const(C)[][] 
>>> paths...) if (isSomeChar!C);
>>
>> this is stodgy, particularly in a console with line wrapping 
>> at 80 chars.
>
>
> To be fair it was the docs page I was reading not a compiler 
> diagnostic, but I did get something a bit shorter from the 
> compiler once.

Oh i see. Then i don't agree. Doc is very nice. The problem is 
that you have to know std.traits and std.range to understand the 
constraints. It's not always obvious but i'd say it's about 30 or 
40 functions.