"Vec<!> should be a zero-sized type, since it has only one state" me: *nodding thoughtfully, reaching under table*pic.twitter.com/FrhuH8pDil
-
Vec<()> already blindly reports usize::max cap, iirc
-
-
Yeah it makes Vec pretty oblivious of ZSTs. len overflow is implicitly managed by capacity checks, and the otherwise dead capacity field is still maintained by some ops for Box<[T]> roundtripping.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.