i.e. it's still not too late to jump the ship you sank with all that syntax bloat (which, we might add, you can bring with you - we built an even bigger boat this time)!
Rust for Rubyists
41–45 of 45 posts
Re: Rust for Rubyists
#42Earlier quoted context omitted.
For me, it's always been select/reject/detect. Even though I know about find_all, it always seemed like the odd one out.
Unrelated! I haven’t talked to you in years. I wrote some DM plugins back in the day. Hope you’re doing well! Are you working on any interesting open source projects?
I don't recognize your handle, but nice that you remember DataMapper!
I'm doing really well, although I did kind of fall off OSS work as I got busier with kids and family stuff. I still hack on lots of different things, but nothing that I've been able to open source. I've been busy learning Haskell these days, although I tend to write Ruby for work.
Re: Rust for Rubyists
#43Re: Rust for Rubyists
#44Earlier quoted context omitted.
Unrelated! I haven’t talked to you in years. I wrote some DM plugins back in the day. Hope you’re doing well! Are you working on any interesting open source projects?
I don't recognize your handle, but nice that you remember DataMapper! I'm doing really well, although I did kind of fall off OSS work as I got busier with kids and family stuff. I still hack on lots of different things, but nothing that I've been able to open source. I've been busy learning Haskell these days, although I tend to write Ruby for work.
Glad all is well!
Re: Rust for Rubyists
#45The filter_map explanation is wrong. .ok() converts a result to an Option, not a boolean. Likewise, filter_map expects an option. That's how it can both filter and map. Docs: https://doc.rust-lang.org/std/result/enum.Result.html#method...
Thanks for the hint. Will fix that and give you some credits.
Edit fixed.