Herb mentions the possibility of `is void` generalizing across pointers, std::optional, and std::future. This seems like it could create ambiguity with a future<void> wherein a non-ready future<void> `is void` and also a ready future<void> `is void`. How should it be handled, I wonder?
https://urlshortenersaresoyesterdaytrythisamazingsuperlongur...
This reminded me of a backend-less filesharing site I once made
https://efokschaner.github.io/furl-unfurl/#/