News for hackers. Stuff that matters.

A comment on Announcing Rust 1.20. Parent comment

Re:Announcing Rust 1.20 by kbenson on Thursday August 31, 2017 @05:56PM (#15144303)
> While f might be a nicer suffice than f32, no suffix is even better.

Well, isn't float in C and C++ platform dependent, and just usually 4 bytes on common platforms? I like the idea of being explicit in the storage type, even if it's slightly more verbose.

[ Parent | on HN ]
Re:Announcing Rust 1.20 by knz42 on Thursday August 31, 2017 @07:40PM (#15144954)
No. ISO C has standardized "float" to 32 bits and "double" to 64 bits. The one that's platform-dependent is "long double".
[ Parent | on HN ]
Re:Announcing Rust 1.20 by ComputerGuru on Friday September 01, 2017 @11:24AM (#15149190)
And, oxymoronically, plain, old long.

In particular, everything but MSVC treats long as 64 bits, but MSVC treats it as 32 bits for backwards compatibility.

However, I haven't used int or long or long long in ten years or so. Thanks to stdint.h support finally making its way to all platforms, it's exclusively sized types like int32_t and uint16_t for me.

[ Parent | on HN ]
Re:Announcing Rust 1.20 by slavik81 on Thursday August 31, 2017 @10:49PM (#15145745)
I might otherwise agree with you, but I find it hard to read when extra numbers are interspersed with the numbers that actually part of the calculation. I feel the readability matters more than the explicitness.
[ Parent | on HN ]