<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>+1</div><div id="AppleMailSignature">I've read the proposal and I've been following the conversation for some days now.</div><div id="AppleMailSignature">I don't have anything else to add to the concerns that have already been discussed, but I would like to reiterate on the fact that having the ,<b>absoluteValue</b>, property but without substituting 'abs' will induce a lot of programers to use it anyway and make mistakes.</div><div id="AppleMailSignature">That's my only concern with it, the rest looks awesome. It is really amazing to see the power of protocols.</div><div id="AppleMailSignature">Thanks for the proposal 👍🏻</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature"><br>Sent from my iPad</div><div><br>On 23 Jun 2016, at 01:52, Chris Lattner via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Hello Swift community,</span><br><span></span><br><span>The review of "SE-0104: Protocol-oriented integers" begins now and runs through June 27. The proposal is available here:</span><br><span></span><br><span> <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0104-improved-integers.md">https://github.com/apple/swift-evolution/blob/master/proposals/0104-improved-integers.md</a></span><br><span></span><br><span>Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at</span><br><span></span><br><span> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br><span></span><br><span>or, if you would like to keep your feedback private, directly to the review manager.</span><br><span></span><br><span>What goes into a review?</span><br><span></span><br><span>The goal of the review process is to improve the proposal under review through constructive criticism and contribute to the direction of Swift. When writing your review, here are some questions you might want to answer in your review:</span><br><span></span><br><span> * What is your evaluation of the proposal?</span><br><span> * Is the problem being addressed significant enough to warrant a change to Swift?</span><br><span> * Does this proposal fit well with the feel and direction of Swift?</span><br><span> * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</span><br><span> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span><br><span></span><br><span>More information about the Swift evolution process is available at</span><br><span></span><br><span> <a href="https://github.com/apple/swift-evolution/blob/master/process.md">https://github.com/apple/swift-evolution/blob/master/process.md</a></span><br><span></span><br><span>Thank you,</span><br><span></span><br><span>-Chris Lattner</span><br><span>Review Manager</span><br><span></span><br><span></span><br><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>