quick quiz! which are incorrect and why cc @spun_offpic.twitter.com/swiTYVVMmb
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
@RichFelker @johnregehr @ch3root @spun_off Justified by what? It would be nice but I don't think there's any guarantee.
@BRIAN_____ @johnregehr @ch3root @spun_off Because it's the same value, and C guarantees round-trip of pointers through uintptr_t.
@RichFelker @johnregehr @ch3root @spun_off I think the C std should say that arithmetic on uint8_t* is equiv to arith on uintptr_t reps...
@BRIAN_____ @johnregehr @ch3root @spun_off This would force impls with advanced ptr models not to define [u]intptr_t at all.
@RichFelker @johnregehr @ch3root @spun_off I'm not sure what you mean then. Isn't that a prereq. for ptr -> uintptr_t math -> ptr?
@BRIAN_____ @johnregehr @ch3root @spun_off No. Without that you can still do all sorts of math treating the values as opaque.
@BRIAN_____ @johnregehr @ch3root @spun_off Hashing or encryption of ptrs, xor linked lists, 'base-relative' diffs for ptrs in shm, etc.
@RichFelker @johnregehr @ch3root @spun_off The standard says only that given a uintptr_t converted from pointer, you can recover pointer.
@BRIAN_____ @johnregehr @RichFelker @spun_off Right. That's why I like one conv (ptr->uint) more than two (ptr->uint & uint->ptr).
@RichFelker @johnregehr @ch3root @spun_off This is why I'm removing all the alignment hacks from *ring* (& BoringSSL, if Google takes 'em).
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.