@searls .dup.reject{}
-
-
-
Replying to @searls
fair point. In which case x = hash.reject(&:bad_thing?) Why complicate matters?
1 reply 0 retweets 0 likes -
Replying to @MarmiteJunction
I deleted the toot because reject used to return an array of entry arrays but now it actually returns the hash
2 replies 0 retweets 0 likes -
Replying to @searls @MarmiteJunction
and I got that wrong at first because reject no longer decomposes {|(k,v)|} correctly, it passes both {|k,v|}. Good times
2 replies 0 retweets 0 likes -
Replying to @searls @MarmiteJunction
`FromIterator` is a good interface to have exist which is separate from `Iterable`/`Iterator`. I wish Ruby had it.
1 reply 0 retweets 1 like -
sounds a bit like the Ennumerable module? Or am I missing something?
3 replies 0 retweets 0 likes -
Replying to @MarmiteJunction @searls
Enumerable just assumes that you want an Array back.
1 reply 0 retweets 0 likes -
(Most langs with that concept allow you to restrict the type of the enumerator.)
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.