In response to a complaint about the fork() API being easy to misuse because error codes and PIDs are overloaded into the same return value instead of separatedpic.twitter.com/Nxz9P17dWS
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
What could be done? Output parameter for the pid? Compiler extension for misuse detection?
At least just use an output parameter for the PID, yeah.
The “improvement of C” has a name: Rust. 
even the C language could still do better than just an int!!! i don’t even think rust would have been necessary to do some bit packing into a struct that has to be intentionally misinterpreted as an int. but the insistence on retroactively explaining their stockholm syndrome = 
To be fair, it's a nice optimization. I was wondering if it'd be possible to make something equally optimized, yet safe. That being said, optimizing 1byte around syscalls is probably pretty useless anyway.
But. It's. Simple. And. Self. Explanatory.
*exasperated sigh* 
But they _are_ separated. Top bit is weak separation, but separation nonetheless. And C will never improve because most people using it have no need for improved C. To them, top bit of an integer is good enough. Generational gap, probably.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.