GNU bug report logs - #32463
27.0.50; (logior -1) => 4611686018427387903

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: andrewjmoreton <at> gmail.com, pipcet <at> gmail.com, 32463 <at> debbugs.gnu.org
Subject: bug#32463: 27.0.50; (logior -1) => 4611686018427387903
Date: Sat, 18 Aug 2018 21:59:49 +0300

> From: Paul Eggert <eggert <at> cs.ucla.edu>
> Date: Sat, 18 Aug 2018 11:48:11 -0700
> Cc: 32463 <at> debbugs.gnu.org
> 
> It would be weird for lsh to act one way for negative bignums, and a different 
> and incompatible way for negative fixnums. Instead, I suggest that we deprecate 
> lsh, as it doesn't make sense any more now that integers have unbounded size. 

It is IMO absurd for us to deprecate a valid and useful operation just
because we added bignums.  If we cannot agree on its semantics for
bignums (which would surprise me), then it is better to make it not
work for bignums at all than deprecate it for fixnums.

> While we're deprecating it, we can make (lsh A B) signal an error if A is a 
> bignum and B is negative, since there's nothing we can do there that is 
> reasonable and is compatible with the fixnum behavior.

If that's the best we can do, fine.  But it doesn't require
deprecating lsh while we are at it.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.