Ran into a weird issue when casting negative floats to u32 @rustlang. Not sure why I'm getting different numbers in some scenarios but not in others? Compare the outputs below... #rustlangpic.twitter.com/MoWzboecC4
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
I'll give this thread a read. Last night I couldn't find much online about f32/f64 > u32/u64 issues. I understand the overflow but just noticed a weird pattern with num_as_u32 specifically. Sometimes 0 or 1 or 32758 or 4136714240 
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.