<div dir="ltr">This pre-proposal needs to answer a few questions before it can really go anywhere:<div><br></div><div>- What sort of mechanism can ++/-- exploit, that "+= 1" or "-= 1" can't, to make the former perform better than the latter? It would be helpful to have at least a vague idea as to whether this is even possible, or else the proposal is meaningless.</div><div><br></div><div>- Exactly how is adding in a faster ++/-- operator going to address Swift's performance problems? For example, how is ++/-- going to make arrays perform better?</div><div><br></div><div>- Why were the (multiple) arguments made in favor of the proposal to remove ++/-- weak or incorrect? What arguments in favor of keeping ++/-- are stronger than their counterparts?</div><div><br></div><div>Best,</div><div>Austin</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 23, 2016 at 6:44 PM, Biala via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="color:#000;background-color:#fff;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:16px"><div><font size="3">Hello,</font></div><div><font size="3"><br></font></div><div><font size="3">I would like to share my opinion on -- and ++ operators...</font></div><div><font size="3"><br></font></div><div dir="ltr"><font size="3"><span style="color:rgb(5,0,0);font-family:Georgia,serif;line-height:20.8px;background-color:rgb(255,254,254)">I think that ++ and — should stay and MUST be implemented as faster operations than += and -=.They have very specific job after all and that is the general understanding. If you fail to implement them as faster operators that will really look as major weakness of SWIFT development team. Swift is still too slow – try working with Arrays so having these faster operators that are very commonly used will be a plus. Another plus will be that you will not break tons of existing code. Breaking existing code is always considered as an architecture weakness and always have a negative impact on the whole developers community – take a look at Microsoft for example they often do that mistake…. Android on the other hand is till that moment always building over the old (however they make other mistakes </span><img alt="😉" src="https://s.w.org/images/core/emoji/72x72/1f609.png" style="max-width:100%;color:rgb(5,0,0);font-family:Georgia,serif;line-height:20.8px;min-height:1em!important;display:inline!important;width:1em!important;margin:0px 0.07em!important;vertical-align:-0.1em!important;padding:0px!important;background-image:none!important;background-color:rgb(255,254,254);background-position:initial!important;background-repeat:initial!important"></font><br></div></div></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div>