bug#8611: fixnum arithmetic should not wrap around

[Paul Eggert <eggert@cs.ucla.edu>]

On 05/03/11 17:31, Stefan Monnier wrote:
> Using floats has only been introduced in order to handle things like
> file sizes larger than 4GB, i.e. the int-to-float conversion currently
> only ever happens for values that come from some C function.

Sorry, I don't follow.  The Lisp reader currently sees "536870912"
and generates a float.  How is that "some C function"?
The Lisp reader's behavior has nothing to do with the stat function
or with file sizes or with anything other than how Emacs itself
is implemented.

I'm just trying to understand the general design principle here.

On further thought:

Would it be better to change Emacs to use bignums if available?
I could do that, using GMP, I suppose.  But surely it should return
bignums consistently everywhere: the Lisp reader, string-to-number,
arithmetic operations, etc.

If bignums aren't feasible for some reason, and floats are our best
approximation, shouldn't floats be used consistently whereever
bignums would otherwise be used?