> What is your evaluation of the proposal? > It makes total sense. It’s a hole to plug in the resilience story. > Is the problem being addressed significant enough to warrant a change to > Swift? > Yes. > Does this proposal fit well with the feel and direction of Swift? > It feels very Swift because it protects users from unknowingly placing themselves at risk of future source-breakage. > If you have used other languages or libraries with a similar feature, how do > you feel that this proposal compares to those? > Not aware of any. > How much effort did you put into your review? A glance, a quick reading, or > an in-depth study? > Several reads and made sure I understood everything. > Thanks, > Ted Kremenek > Review Manager > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
