The more @elixirlang I write, the more distaste I have for with. My issue with it is that it removes cohesion in your unhappy path. All of a sudden, you are handling errors without the context that created them.
I've seen this pattern where you do with {:step, result} <- {:step, action()} and then use that to pull out the contextual error paths in the else block, which I also dislike as it makes the code so dense.
What do I prefer? Maybe a nested case here and there isn't so bad. With's are fine when you just want to result the unhappy path as is, or the error logic is pretty much _ -> do_something()

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Dave Lucia

Dave Lucia Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!