no-autodecode -- game plan

[aberba]

On Wednesday, 19 August 2020 at 15:39:58 UTC, H. S. Teoh wrote:
> On Wed, Aug 19, 2020 at 09:35:34AM -0400, Andrei Alexandrescu 
> via Digitalmars-d wrote:
>> On 8/19/20 8:23 AM, Steven Schveighoffer wrote:
> [...]

> When we get to the point where the entire Phobos can be 
> compiled with no-autodecoding, *then* we can gauge the true 
> extent of breakage (by compiling public D repos with 
> autodecoding on -- *experimentally*) to obtain some REAL DATA 
> on which to base decisions, instead of gut feelings and other 
> totally subjective criteria, and thereby be in a much better 
> position to make a sane decision about where to go from there.
+ 1

> If we absolutely do not want to break backward compatibility, 
> then *at that time* we can freeze the current std.*, make a 
> copy of everything in std.v2021, turn on no-autodecoding for 
> the latter, and go from there.

At that time, it might not be a bad idea either. Eventually D 
will need something like this to ensure it's not held behind by 
future mistakes (which definitely will happen)...as long as it 
can be corrected in the next version of std. Guess we'll see when 
that time to comes.