• Lucia Cojocaru (8/8) May 20 2017 Hi,
• Timon Gehr (4/11) May 20 2017 I don't think there is.
• Timon Gehr (3/17) May 20 2017 To back that up, there are no dates specified in the relevant documentat...
• Seb (4/6) May 20 2017 If you or anyone wants to help pushing the deprecation phase,

Lucia Cojocaru <lucia.mcojocaru gmail.com> writes:

Hi,

I see array.sort and array.reverse are still in the deprecation 
phase. Is there any planned date for their removal?

Deprecation: use std.algorithm.sort instead of .sort property
Deprecation: use std.algorithm.reverse instead of .reverse 
property

Thanks,
Lucia

Timon Gehr <timon.gehr gmx.ch> writes:

On 20.05.2017 12:52, Lucia Cojocaru wrote:
 Hi,

 I see array.sort and array.reverse are still in the deprecation phase.
 Is there any planned date for their removal?

 Deprecation: use std.algorithm.sort instead of .sort property
 Deprecation: use std.algorithm.reverse instead of .reverse property

 Thanks,
 Lucia

I don't think there is.

There is this PR that turns the deprecation messages into compilation 
errors: https://github.com/dlang/dmd/pull/6554

Timon Gehr <timon.gehr gmx.ch> writes:

On 20.05.2017 13:23, Timon Gehr wrote:
 On 20.05.2017 12:52, Lucia Cojocaru wrote:
 Hi,

 I see array.sort and array.reverse are still in the deprecation phase.
 Is there any planned date for their removal?

 Deprecation: use std.algorithm.sort instead of .sort property
 Deprecation: use std.algorithm.reverse instead of .reverse property

 Thanks,
 Lucia

 I don't think there is.

To back that up, there are no dates specified in the relevant documentation:
https://dlang.org/deprecate.html

 There is this PR that turns the deprecation messages into compilation
 errors: https://github.com/dlang/dmd/pull/6554

Seb <seb wilzba.ch> writes:

On Saturday, 20 May 2017 at 11:23:54 UTC, Timon Gehr wrote:
 There is this PR that turns the deprecation messages into 
 compilation errors: https://github.com/dlang/dmd/pull/6554

If you or anyone wants to help pushing the deprecation phase, 
please feel to adopt this PR, do the final polishing and get it 
merged _before_ the 2.075 release ;-)