<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">In principle, having Float, Float32, and Float64 and no “Double” at all seems highly sensible to me.</div><div class=""><br class=""></div><div class="">In practice, the migration cost of changing the meaning of Float from “32-bit” to “platform preferred size” seems like a potential deal-killer.</div><div class=""><br class=""></div><div class="">P</div><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 5, 2016, at 2:25 PM, Alex Johnson via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="">Just to clarify: I was suggesting removing the name "Double" and giving a different meaning to the name "Float".</div><div class=""><br class=""></div><div class="">~ Alex</div><div class=""><br class=""></div><div class="gmail_quote">On Tue, Jan 5, 2016 at 11:51 AM, Chris Lattner <span dir="ltr" class=""><<a href="mailto:clattner@apple.com" target="_blank" class="">clattner@apple.com</a>></span> wrote:</div><div class="gmail_quote"><br class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">These are functionally different cases. We are *omitting* a C feature by removing ++ and --. This proposal included keeping the name “Double” but giving it a different meaning.</div></div></blockquote><div class=""><br class=""></div><div class=""><br class=""></div></div>
</div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=zCg-2FSGF9Wk188a6c55kLyEbrj7YhaXxFEHM-2F-2B0YAlzWzKXoDY26zqW-2BjCfwcy9NNyJcCwNQZi0Ut6pbnWJVy7NSW5bfutP-2F5Ii1-2FKXoiSlbXrz8j6rgDaLEh2xOmI5s2biPybsyLTWlca5uJ-2FMMIcDIzQqmUJWHqdD4xQoLBh-2B9nuKzc931JpR-2F69-2FFjr3iETv1HEWwQS8Nbxsx0OR-2FGISAeISwntkcibQBnu4JYSZ0-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>