<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=""><br class=""><blockquote type="cite" class="">On 06 Jan 2016, at 03:08, Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.com</a>> wrote:<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Jan 5, 2016, at 4:41 PM, Janosch Hildebrand via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class="">I also think that Float and Double are not ideal type names but I also agree with many of the concerns that have been raised.<br class=""><br class=""><br class="">Why not simply use (the existing) Float32 and Float64 while keeping everything else equal?<br class=""></blockquote><br class="">What perceived problem are you solving?<br class=""><br class="">-Chris<br class=""></blockquote><br class="">a) That ‘Double’ is not a great type name and the Float/Double combination is inconsistent naming.<div class="">(b) Trying to direct this discussion into a (from my point of view) more reasonable direction; i.e. away from 64-bit Float and CGFloat-reborn)<br class=""><div class=""><br class=""><br class="">Although I wouldn’t go so far as to call Float/Double a problem, more of a nitpick.</div><div class="">I hadn’t given it any thought really before this thread so this is just me thinking out loud…<div class=""><br class="">To me, FloatXX has the following advantages:<div class=""><ul class="MailOutline"><li class="">Consistent naming: Float16, Float32, Float80, Float128</li><li class="">The names contain information about the type (what is it, how large is it) that is very accessible</li><li class="">Aligns nicely with the integer types</li></ul><div class=""><br class=""></div><div class="">And the following obvious disadvantages:</div><div class=""><ul class="MailOutline"><li class=""><b class="">Float and Double are much more prevalent </b>(</li><li class="">Float and Double are shorter</li></ul><div class=""><br class=""></div></div><div class=""><br class=""></div><div class="">However I think the decision to go with Float/Double is very reasonable as these advantages are pretty minor and on the other end of the scale is a lot of historical precedent. Hence the ‘can we get people used to and using FloatXX while still retaining Float & Double?’ ;-)</div><div class=""><br class=""></div>- Janosch</div></div></div></div></body></html>