> What is your evaluation of the proposal?
+0.75
I agree that this is better than what we have now. I wonder though, if we
should just mark it as “a change we want to make”, and then actually make the
change at the same time as we add submodules, etc… I would hate to have to
make another small change to this in the future to accommodate those features
right after changing this again now. (or worse, I would hate to feel like we
were blocked from making necessary changes in the future because of churn
caused by this).
> Is the problem being addressed significant enough to warrant a change to
> Swift?
Yes, I think so.
> Does this proposal fit well with the feel and direction of Swift?
Yes
> If you have used other languages or libraries with a similar feature, how do
> you feel that this proposal compares to those?
Swift does it’s own thing here, but I like it.
> How much effort did you put into your review? A glance, a quick reading, or
> an in-depth study?
A fair amount of thought during the discussion. A little bit right now.
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
