5 ms·
I haven't had a chance to work with Swift much yet, but I'm actually very glad for their reasonings. The only issue I might gripe with is the single quotes, but
by bruxis 11y ago
I haven't had a chance to work with Swift much yet, but I'm actually very glad for their reasonings. The only issue I might gripe with is the single quotes, but I get the unicode perspective.
- weaksauce 11y agoHow often are you really making characters? Single quote for unescaped string literals is used way more often in my world and it's a feature of ruby, base et al. and other languages. Character("X") isn't that bad for something used minimally.
- yeukhon 11y agoI argue that even in the case of char, why so cheap now to reserve a type for char instead of using unicode? I get it, sometimes you have requirements where char type is cheaper to use, but on iPhone a few extra bytes won't kill.
- weaksauce 11y agowell it's supposed to be a systems language so it makes sense to have all types available. you could ask the same of Int8 being in the language when pretty much all processors nowadays are 64bit.