> * What is your evaluation of the proposal?
I really like this proposal as it reduces the surprise factor while continuing
to promote convention over configuration. It also mirrors the way people are
often would like to name their test modules.
> * Is the problem being addressed significant enough to warrant a change to
> Swift?
Yes, it's a natural simplification that is fairly forward thinking
> * 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?
No.
> * How much effort did you put into your review? A glance, a quick reading,
> or an in-depth study?
Quick reading.
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
