> Once someone starts shipping something that depends on a feature they get
> very grumpy when it gets taken away.
Well, it happened before, and people's life went on without tuple splat and
currying… ;-)
I don't think an open Beta would add that much value on its own — but imho the
aspect of temporary acceptance could improve the process:
Instead of being implemented right away (in theory ;-), changes that really
alter the shape of Swift could be delayed for a longer period to allow other
proposals to be build on them.
Such a proposal would define the general direction, and it should be the goal
to incorporate it in a future release — but if it turns out that the original
path has issues that are revealed by constructs built on top of it, the initial
idea could still be improved without causing churn.
As a sidenote, originally I merely thought SE-0025 is nonsense, and I just
didn't oppose strongly because, after all, replacing "private" with
"fileprivate" isn't that terrible. But during the discussions for Swift 4, I
changed my mind, and now I think that with some follow-ups, the concept of
scope-private could have become really useful...
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
