Miss Dada  🏳️‍⚧️

or it points to merging Future with Option/Result being completely muddied and problematic!

So why is the first better than the second? https://gist.github.com/sgrif/f967116241999765e3f46506215ad8ae …

also objectively this is the best x.flatMap { (y) in do_stuff(y) .flatMap { do_more_stuff(y, $0) }}

Also that should probably be `flattenIntoSingleLevelAfterMappingWith: (y) in ...`

You're right, &x.ft_mp(&mut || {;};);; is much more information-dense

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))

self.current_header.as_ref().map(|s| &**s).unwrap_or(""); gets me every time

Yeah, people complain about Swift having custom operators, but when the alternative is…that…