Comment 2 for bug 1099087

Changing back to "new" from "won't fix" until this is discussed with other core devs.

It may be possible to allow an option config parameter to control this behavior. If that's an acceptable solution to all of the core devs, or if there is a better on, we can accept the bug and move forward.

However, if the core devs determine that this is the functionality for swift api v1 and it won't be changed, even with a config option, I will re-close this as "won't fix"