> On Nov 27, 2017, at 2:56 AM, Tino Heth <2...@gmx.de> wrote: > > >> The implementation is straight-forward and (IMO) non-invasive in the >> compiler. > At least it’s smaller than I would have expected — but I don’t have the > overview to judge the consequences to the compiler. > > However, the impact those two proposals have on Swift is imho huge, and as > the whole story is quite special for several reasons, there’s an elephant in > the room that shouldn’t be ignored: > - What would you do if the proposal isn’t accepted?
Circle back and try to solve the problem another way? It depends on why it would be rejected. > - What does core think you would do in this case? The core team officially weighs in after the review process, not before. > - What impact will that speculation have on the decision? It should be zero. The point of the review process is to weigh the merits of a proposal. In any case, FWIW, I don’t find your email very helpful, since you’re not actually talking about technical merits of the proposal: you’re encouraging speculation about politics :-) -Chris
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
