Downgrade existential `any` errors to warnings until a future language mode

Regardless of whether this is a new pitch or hidden under feature flags or whatever, I think people are asking that this anomaly be removed for the sake being able to implement linters which would be a win and could be delivered in short order without a source break.

My opinion is the situation with SE-0335 needs to be clarified as my impression is that it should be formally withdrawn if the feature flag is never going to be turned on. Talk of eliding to some (which is not feasible if you look at real code) makes me nervous this unfortunate chapter in Swift evolution has not reached its final resting place. Adding the any keyword, fine. Making it compulsory would have been (and would still be) massively source breaking and an order of magnitude more disruptive than any of the other Swift 6 migration problems discussed of late.

1 Like