syntax and extreme preference for method chaining bullshit, which means you have different functions to remember for slightly different use cases, instead of just making it easy to compose standard control flow (which is typically awkward). You do know the differences between methods in this incomplete list of Result methods, right anon? (Result and Option being some of the most ubiquitous types in the damn language)
expect
expect_err
flatten
inspect
inspect_err
into_err
into_ok
is_err
is_err_and
is_ok
is_ok_and
iter
iter_mut
map
map_err
map_or
map_or_else
ok
or
or_else
Most of these names should indicate to you that they’re composing several things together, and imho shows the language design drove a bunch of logic into an array of similar but different methods instead.
All in all I overall like rust, the type system is fucking great.
@Darren I also don't know why people are mad at Adam. It wasn't my intent for Adam to be portrayed as some kind of comic book villain, it's silly.
So that it is clear, it was me who made the decision. The issue was clear and stated in public, so I just took the only viable course of action to resolve the problem. I anticipated that people would click my profile, scroll back, see the immediately preceding conversation, and have context. In hindsight, I could have been more explicit about it.