> On Apr 17, 2017, at 18:53, Nevin Brackett-Rozinsky via swift-evolution 
> <[email protected]> wrote:
> 
> At a meta-level, since mistakes like SE–0025 will be much more costly in the 
> source-stable future, we ought to consider adding a step to the Swift 
> Evolution process whereby accepted proposals are implemented in a beta 
> version of Swift, and a second review period can happen if new problems 
> become apparent in actual usage that were unforeseen during the initial 
> discussion. That way we are much more likely to catch emergent issues before 
> release.

I see the benefit, but I'd have to think about it more before claiming to have 
an informed opinion.

- Dave Sweeris

_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to