asciilifeform woke up from dream where mircea_popescu finally showed him the antigravity glove. which was the only piece of tech he had brought from the distant future where ha had been born
asciilifeform: ^ www that had the dumps from tardstalk, 'adultfriendfinder', buncha others
asciilifeform: then I'll be wrong. But I am not wrong."'
asciilifeform: elsewhere in heathendom, http://archive.is/kfQaT >> '"Leakedsource is down forever and won't be coming back," a person using the handle LTD wrote Thursday in an online forum. "Owner raided early this morning. Wasn't arrested, but all [solid state drives] got taken, and Leakedsource servers got subpoenaed and placed under federal investigation. If somehow he recovers from this and launches LS again,
asciilifeform: there is deep wisdom in this here this.
asciilifeform: regehr is (or at least was) solid thinker, and the problem being spoken of, actually exists. there are archs with no sane overflow handling. and hence why gcc doesn't use, apparently, carry flag.
asciilifeform: if tomorrow knuth starts to harp about slow $shitlang, mircea_popescu will throw out his copy of aop ?
asciilifeform: first time i see the d00d mention shitlangs. but the overflow thing affects shitlangs just as much as sanelangs.
asciilifeform: actually that second thing only half-happened, you only get a second machineword out of mul on any known chip
asciilifeform goes to the b00kz room to fetch 'ada 2012 rationale', to learn whether he is complete moron, or wat.
asciilifeform: shl can give you as much overflow as you like.
asciilifeform: mircea_popescu: there's another op defined for ring of integers, that is SHL
asciilifeform: but iirc the reason why we do not have this behaviour by default is that there are boxes that don't give you the upper bits of an overflowing mul. or set the carry.
asciilifeform: mircea_popescu has mega-point --- you CAN make range-checked (at least for upper bound of range not exceeding the native fixint size by more than factor of 2) behaviour on x86