If `int` has the wrong size ...?

l0kod · 2014-09-13T18:01:09.002Z

+1 for isize and usize because it make sense and is quite similar to C.

benh:

If we go for isize, usize, We should change the suffixes away from i/u too, since them being that short only really makes sense if we want to push people towards habitually using them.

+1 to encourage fixed-size integer

CloudiDust:

I think the same but am a little concerned about is and us being two actual words with other meanings, especially is. In practice this should not be a problem though.

This suffixes seems awkward but do we really need suffixes for isize and usize?

Moreover, the discussion about RFC #212 seems to favor default integer and float to i32 and f64.

l0kod · 2014-10-18T17:09:33.287Z

Added two more int/uint related bugs (capnproto):

github.com/rust-lang/rust

Issue: Encourage fixed-size integer

opened by l0kod on 2014-08-12

closed by steveklabnik on 2015-01-12

The #6023 force to use a type suffix for integers. As discussed in rust-lang/rfcs#115 and #9940, the int and uint should...

l0kod · 2014-10-18T17:09:58.608Z

Of course, renaming int and uint to something more meaningful is a breaking change. Is there something plan for the Rust 1.0 milestone?

l0kod · 2014-11-13T08:22:30.992Z

New RFC: https://github.com/1fish2/Rust-rfcs/blob/int-name/active/0000-int-name.md

Cf. https://github.com/rust-lang/rfcs/pull/161

l0kod · 2014-11-13T20:06:01.171Z

New PR: https://github.com/rust-lang/rfcs/pull/464

l0kod · 2014-12-24T13:10:47.154Z

Continued in A tale of two’s complement.

pnkfelix · 2019-03-25T08:22:50.560Z

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.