Is it time for D 3.0?

Wed Apr 1 12:43:51 UTC 2020

On Wednesday, 1 April 2020 at 09:40:34 UTC, John Colvin wrote:
> So many things in D are breaking changes. Because of 
> introspection and __traits(compiler,...) etc. almost any bug 
> fix can break someone's code. Even introducing an entirely 
> disjoint overload for a function can be a breaking change.
>
> It would be an interesting but daunting (impractical?) task to 
> characterise what is considered "API" and what is 
> "implementation detail" in phobos.

Has there ever been any kind of systematic effort to record and 
categorize those sorts of introspection-based breakages?  I'm 
wondering if there are any regularities to what breaks that would 
help us avoid them more rigorously.