<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div 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.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Why not simply use (the existing) Float32 and Float64 while keeping everything else equal?</div><div class=""><br class=""></div><div class="">So as a first step we could encourage the use of Float32/Float64 over Float/Double:</div><div class=""><ul class="MailOutline"><li class="">Make Float/Double typealiases for Float32/Float64 instead of the reverse which is true today</li><li class="">Use Float32/Float64 in documentation and example code</li><li class="">Perhaps add a note to the documentation for Float/Double that the Float32/Float64 types should be preferred</li><li class="">...</li></ul></div><div class=""><br class=""></div><div class="">This would not break any existing code and I think would be a positive change in the long term.</div><div class="">Also this might have a better chance to be accepted as a proposal and by the community at large.</div><div class=""><br class=""></div><div class="">Making Float32/Float64 the officially preferred types should still help their adoption a lot without the pains involved in removing Float/Double.</div><div class=""><br class=""></div><div class="">And the deprecation and eventual removal of Float/Double could still be considered separately either now or down the road if people actually adopt Float32/Float64. Also migration would be very simple in this case (and stragglers could simply create their own Float/Double typealiases).</div><div class=""><br class=""></div><br class=""><div class="">
<div class="">- Janosch</div>
</div>
<br class=""></body></html>