One trick to get out of this is to wrap any function with an asynchronous interface with pollster::block_on which turns the call back into exactly how it would have run if it had been synchronous (which leads to no color leaking).
Yes, easy enough but annoying. Going the other direction (async -> sync) is a bit more problematic though. Now you've got to wrap things in spawn_blocking(), which isn't nearly as benign.
In 2007 carriers were giving away phones for free to those signing up for a plan, and the initial $500 price tag was mocked and lambasted as being way too expensive. There were all kinds of phones that it was far more than 10x pricier than.
> VR headsets are a gimmick, a novelty, they bought one, tried it, put it on a shelf.
Most shelf ridden cast off Quest 2s are there because they were found to be grainy and nausea inducing. A leap in latency and resolution could very well prompt revaluation in the space.
Had this same experience several times in various projects and in all sorts of IDEs, major pain. If it’s helpful, I recently came across the 10x c++ editor project, which has the best c++ code completion experience I’ve seen by a huge margin. Some rough edges UI wise, but it’s still in beta
reply