[dmd-beta] Preparing for dmd 2.066 beta
Brad Roberts via dmd-beta
dmd-beta at puremagic.com
Tue Jul 8 11:59:48 PDT 2014
As always, the best and most appropriate way to make sure something isn't lost (and comments at the
end of a closed pull request definitely fall into the likely to be lost category) is to file a bug
report.
On 7/8/14, 4:39 AM, Steven Schveighoffer via dmd-beta wrote:
> Just to bring this up again, this still is not fixed.
>
> https://github.com/D-Programming-Language/dmd/pull/3711#issuecomment-48325105
>
> -Steve
>
> On Jun 26, 2014, at 10:49 PM, Steven Schveighoffer via dmd-beta <dmd-beta at puremagic.com> wrote:
>
>> We cannot release without either reverting the changes to AA requirements, or making it so we are sure code that was flawed, but previously worked, is flagged as an error.
>>
>> See this comment: https://github.com/D-Programming-Language/dmd/pull/3599#issuecomment-45275443
>>
>> Code that previously (incorrectly) relies on the fact that AA code only calls compare, and defines only opCmp and not opEquals, will SILENTLY BREAK if we release today.
>>
>> This is not acceptable. It needs to break, but break loudly, and not compile.
>>
>> -Steve
>
>
> _______________________________________________
> dmd-beta mailing list
> dmd-beta at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>
More information about the dmd-beta
mailing list