ah, so basically just "filter, but our type system is too good to admit it"
-
-
Replying to @Gankra_ @JakeGoulding
oh no wait, our type system isn't https://doc.rust-lang.org/std/iter/trait.Iterator.html#method.filter_map …
3 replies 0 retweets 0 likes -
Replying to @Gankra_ @JakeGoulding
flat_map is like fold -- it's a complete friggin' mess because it's some super generic thing that obfuscates everything!
2 replies 0 retweets 0 likes -
-
Replying to @JakeGoulding
I think multiplicity is very significant for how we think of things. while/for/loop/if all exist and are useful to distinguish
2 replies 0 retweets 0 likes -
Replying to @Gankra_
I agree that first-class multiplicity is useful to have, but so is having an abstraction over it.
1 reply 0 retweets 0 likes -
Replying to @JakeGoulding
it's always nice to have an abstraction when you want it, but many abstractions are *completely friggin confusing*.
1 reply 0 retweets 1 like -
Replying to @Gankra_ @JakeGoulding
one should generally avoid applying unifying abstractions unless there's a compelling reason to. Not just because it exists.
2 replies 0 retweets 1 like -
Replying to @Gankra_ @JakeGoulding
There isn't much reason to try to unify optional values and lists... and the little amount Rust has done has given me bugs!
1 reply 0 retweets 0 likes -
Replying to @Gankra_ @JakeGoulding
namely the fact that `for y in http://list.next () { ... }` compiles.
1 reply 0 retweets 0 likes
Although it would be silly to deny that this particular aspect is an annoying catch. At least Clippy helps: https://is.gd/cQwbhm
-
-
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.