[swift-evolution] Thoughts on clarity of Double and Float type names?
clattner at apple.com
Tue Jan 5 13:51:28 CST 2016
> On Jan 5, 2016, at 11:20 AM, Goffredo Marocchi <panajev at gmail.com> wrote:
>> That said, personally, my feeling is that the momentum here in the broad family of C languages (including things like Java) is very strong, and that diverging from that would be extremely problematic. I don’t see any “active" problems with our current names. If this is a matter of aesthetics, or an attempt to align with Ruby/Python/Go instead of C/Java etc, then this seems like the wrong direction for Swift.
> Losing alignment to C-like paradigms is a valid concern, but then removing unwary decrement and increment operators feels out of place... Sad to have seen it culled.
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.
There are good and bad parts of C syntax. The goal is not to cargo cult all of the bad parts of C into Swift, it is to keep the good parts and discard the bad parts. For things that could go either way, we should keep alignment with C.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution