SE-0042 was formally accepted more than three years ago. However, since the proposal was accepted before having a working implementation was a requirement, and the change would be source breaking, and also require massive rewrites of the compiler; it is now clear that this proposal will never actually be implemented. It has been obvious for a long time.
In April of 2018, Joe Groff wrote:
And in October of that same year, Matthew Johnson added
Yet, the proposal is still listed as "accepted", and SR-1051 is still marked "unresolved" (and even with "medium" priority). The Swift Evolution Status page gives the impression that it will actually be implemented in some future version of Swift.
Is is time to formally mark SE-0042 as "Revoked", SR-1051 as "won't fix"?
Does it require a formal SE proposal to revert the behaviour, and present a null-implementation? Currently, the de-facto direction of Swift and its formally accepted direction, are out of sync.