"Vec<!> should be a zero-sized type, since it has only one state" me: *nodding thoughtfully, reaching under table*pic.twitter.com/FrhuH8pDil
-
-
-
Replying to @sgrif
Vec<()> already blindly reports usize::max cap, iirc
2 replies 0 retweets 0 likes -
Replying to @Gankra_
Tbh if the compiler could optimize that, &str could theoretically not exist
1 reply 0 retweets 0 likes -
-
Replying to @Gankra_
&'static String, we know cap always == len and never changes. Compiler could theoretically eliminate cap in other cases as well. Box would be the hard one
1 reply 0 retweets 0 likes -
Replying to @Gankra_
Sounds like a personal problem to me
5:28 PM - 15 Jan 2018
from Albuquerque, NM
0 replies
0 retweets
3 likes
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.