I proposed the same here. The argument back then was that it could alleviate bikeshedding, which in of in itself is of course no argument to add such a drastic change to the language.
In addition to your use case, another one would be as a mechanism for dealing with deprecation without code duplication (or wrapping). The recently introduced MigrationSupport.swift file is full of them.