Also that should probably be `flattenIntoSingleLevelAfterMappingWith: (y) in ...`
-
-
Replying to @sgrif @JakeGoulding
You're right, &x.ft_mp(&mut || {;};);; is much more information-dense
3 replies 1 retweet 2 likes -
Replying to @jckarter @JakeGoulding
Lines like https://github.com/diesel-rs/diesel/blob/master/diesel/src/query_builder/mod.rs#L106 … are my favorite... (which could have been (&**self).to_sql(out))
1 reply 0 retweets 0 likes -
self.current_header.as_ref().map(|s| &**s).unwrap_or(""); gets me every time
4 replies 0 retweets 0 likes -
Yeah, people complain about Swift having custom operators, but when the alternative is…that…
2 replies 0 retweets 0 likes -
self.current_header.as_ref().map { &**$0 } ?? ""; seems like the best Swift's current stuff gets you?
2 replies 0 retweets 0 likes -
as_ref() and &** seem like they could be implicit. Usually only one of borrow or move is possible in context…
2 replies 0 retweets 0 likes -
Just TBC I'm not hating on Rust. Getting the model right and adding sugar later is absolutely the right thing
2 replies 0 retweets 2 likes -
Replying to @jckarter @JakeGoulding
I am. The fact that I can turn String to &str implicitly but not Option<String> into Option<&str> bugs me
2 replies 0 retweets 1 like -
Replying to @sgrif @JakeGoulding
I can see why they're conservative w/implicit bhvr. It can have unexpected side effects and is hard to back out
1 reply 0 retweets 0 likes
Thus is true. The pattern matching case I complain about is far more complex than fits in 140 chars
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.