Optimizing Java using D

[via Digitalmars-d]

On Sunday, 22 June 2014 at 17:34:15 UTC, Nick Sabalausky wrote:
> On 6/21/2014 1:40 AM, Tofu Ninja wrote:
>>
>> On another note, if someArray.sort() calls the built in sort 
>> even when
>> std.algorithm is imported, then most definitely built in sort 
>> needs to
>> go, I can see plenty of times where people would not even 
>> realize they
>> were calling the wrong sort or even that there was an error in 
>> their code.
>
> If there's any lingering reasons why built-in sort might still 
> need to exist (I wouldn't know), then maybe it could get moved 
> into object.d (perhaps by internally being renamed ex. __sort, 
> with a "sort" wrapper in object.d?). That way it should at 
> least trigger a conflict with std.algorithm.sort instead of 
> shadowing it.

But then it wouldn't be callable with UFCS, no?