On Saturday, 14 September 2013 at 11:00:26 UTC, Jacob Carlborg wrote:
> On 2013-09-14 00:10, simendsjo wrote:
>
>> But I doubt many people here agree D2 is in beta and will allow breaking
>> existing code in ways that changing the aforementioned features would do.
>
> DMD breaks code in every single release. All 2.05x and 2.06x releases have caused code breakage for DWT in some way or another.

I know each release breaks code in various ways, but if 2.064 was to redesign is() and __traits() without maintaining backwards compability I think many people would fork/leave D altogether. So I'm not sure if I would call it beta even if each release breaks code due to bugs, bugfixes, removing code that shouldn't be allowed i the first place etc.

On Saturday, 14 September 2013 at 11:29:33 UTC, simendsjo wrote:
> On Saturday, 14 September 2013 at 11:00:26 UTC, Jacob Carlborg wrote:
>> On 2013-09-14 00:10, simendsjo wrote:
>>
>>> But I doubt many people here agree D2 is in beta and will allow breaking
>>> existing code in ways that changing the aforementioned features would do.
>>
>> DMD breaks code in every single release. All 2.05x and 2.06x releases have caused code breakage for DWT in some way or another.
>
> I know each release breaks code in various ways, but if 2.064 was to redesign is() and __traits() without maintaining backwards compability I think many people would fork/leave D altogether. So I'm not sure if I would call it beta even if each release breaks code due to bugs, bugfixes, removing code that shouldn't be allowed i the first place etc.

Then tell me, what do you call it then? final? ;)

On Saturday, 14 September 2013 at 11:45:38 UTC, Namespace wrote:
> On Saturday, 14 September 2013 at 11:29:33 UTC, simendsjo wrote:
>> On Saturday, 14 September 2013 at 11:00:26 UTC, Jacob Carlborg wrote:
>>> On 2013-09-14 00:10, simendsjo wrote:
>>>
>>>> But I doubt many people here agree D2 is in beta and will allow breaking
>>>> existing code in ways that changing the aforementioned features would do.
>>>
>>> DMD breaks code in every single release. All 2.05x and 2.06x releases have caused code breakage for DWT in some way or another.
>>
>> I know each release breaks code in various ways, but if 2.064 was to redesign is() and __traits() without maintaining backwards compability I think many people would fork/leave D altogether. So I'm not sure if I would call it beta even if each release breaks code due to bugs, bugfixes, removing code that shouldn't be allowed i the first place etc.
>
> Then tell me, what do you call it then? final? ;)

I've been waiting it to be final since 2007 :)
Getting better by leaps and bounds though.

On Saturday, 14 September 2013 at 13:14:50 UTC, simendsjo wrote:
> On Saturday, 14 September 2013 at 11:45:38 UTC, Namespace wrote:
>> On Saturday, 14 September 2013 at 11:29:33 UTC, simendsjo wrote:
>>> On Saturday, 14 September 2013 at 11:00:26 UTC, Jacob Carlborg wrote:
>>>> On 2013-09-14 00:10, simendsjo wrote:
>>>>
>>>>> But I doubt many people here agree D2 is in beta and will allow breaking
>>>>> existing code in ways that changing the aforementioned features would do.
>>>>
>>>> DMD breaks code in every single release. All 2.05x and 2.06x releases have caused code breakage for DWT in some way or another.
>>>
>>> I know each release breaks code in various ways, but if 2.064 was to redesign is() and __traits() without maintaining backwards compability I think many people would fork/leave D altogether. So I'm not sure if I would call it beta even if each release breaks code due to bugs, bugfixes, removing code that shouldn't be allowed i the first place etc.
>>
>> Then tell me, what do you call it then? final? ;)
>
> I've been waiting it to be final since 2007 :)
> Getting better by leaps and bounds though.

But still a long long way. :)