Ever seen an object larger than SIZE_MAX bytes? How about SIZE_MAX * SIZE_MAX bytes on x86-64?pic.twitter.com/AncfvROab0
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
So I agree there's a bug that needs to be fixed, but the proper fix is ensuring the offending objects can never arise.
So all objects in all programs are to be restricted to <=PTRDIFF_MAX due to a potential problem of the - operator\
with large arrays of chars in some programs. Doesn't look like a proper fix to me.
Not "some programs". Due to complete inability to use an operator that's widely used and should be usable.
"This operator works, but it could overflow & yield UB, & you have no way of testing it does" = bug in C standard.
Any non-crap implementation of C will avoid this bug simply by not generating cases that can overflow.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.