Why should optional closures be special? From a point of view of the user of your apis it is an undefined behaviour, and you must assume no-matter-what that it will escape.
Leave aside poor choice of documentation and keywords, because with this reason you could even argue that we don't need @escaping at all. This ambiguity that optional creates with closures should in my opinion be fixed.
Drop the new keyword, please. The conversation evolved and we agreed on the fact that we can do it having optionals propagating escapability (which is what I proposed in the first pitch on this matter)
2 Likes