Major performance problem with std.array.front()

[Abdulhaq]

On Monday, 10 March 2014 at 14:05:39 UTC, dennis luehring wrote:
> Am 07.03.2014 03:37, schrieb Walter Bright:
>> In "Lots of low hanging fruit in Phobos" the issue came up 
>> about the automatic
>> encoding and decoding of char ranges.
>
> after reading many of the attached posts the question is - what
> could be Ds future design of introducing breaking changes, its
> not a solution to say its not possible because of too many 
> breaking changes - that will become more and more a problem of 
> Ds evolution
> - much like C++

I'm a newbie here but I've been waiting for D to mature for a 
long time. D IMHO has to stabilise now because:
* D needs a bigger community so that the the big fish who have 
learnt the ins and outs don't get bored and move on due to lack 
of kudos etc.
* To get the bigger community D needs more _working_ libraries 
for major toolkits (GUI etc. etc.)
* Libraries will cease to work if there is significant change in 
D, and then can stay broken because there isn't the inertial mass 
of other developers to maintain it after the intial developer has 
moved on. You can see that this has happened a LOT
* Anyway the D that I read about in TDPL is already very exciting 
for programmers like myself, we just want that thanks.

Breaking changes can go into D3, if and whenever that is. Keep 
breaking D2 now and it risks just being forevermore a playpen for 
computer scientist types.

Anyway who cares what I think but I think it reflects a lot of 
people's opinions too.