thojanssens1

thojanssens1

Sometimes you have two versions for a function, one returning a tuple (ok or error tuple), and the other raising. The latter will be then have a bang ! suffix.

For example Map.fetch/2 and Map.fetch!/2

But not every function that raise will have the bang suffix. Random example: Ecto.Changeset.put_assoc/4.
If the given key is not found it will raise, but the function still has no bang !.

What is the rule as to when to adopt the bang for your functions and when not?

First 3 of 3 Posts Switch mode

wolf4earth

wolf4earth

From my perspective a good rule of thumb is:

  • is there a non-raising version of the function?
  • is it a realistic scenario that the passed data might lead to a raised error?

Let’s inspect your examples with these rules.

Map.fetch!/2

  • is there a non-raising version of the function?
    Yes - Map.fetch/2
  • is it a realistic scenario that the passed data might lead to a raised error?
    Yes - as Map operates on maps, these might or might not contain the given key

Ecto.Changeset.put_assoc/4

  • is there a non-raising version of the function?
    No
  • is it a realistic scenario that the passed data might lead to a raised error?
    Noish - passing an invalid key is certainly a programmer error and should be caught as early as possible

So in that sense it makes sense that Map.fetch!/2 has a bang and Ecto.Changeset.put_assoc/4 has not.

chulkilee

chulkilee

Having no bang suffix doesn’t mean it will never raise an error for any input.

  • If my function needs to return error tuple - then make it ok/error tuple, not returning nil.
  • If I need the function used in pipe a lot (by the nature of the function - such as it’s for data transformation) - then create bang version.

There is another school of thought - e.g. make every function to return ok/error tuple and use “optional” type like wrapper.

christhekeele

christhekeele

Bangs in Elixir, as well as Ruby, are a way of indicating there is a similar, safer way to perform an operation. The intuition I’ve developed around them is:

  • When writing an API, present bang variants of functions for operations where both safe and unsafe versions have strong use-cases.

  • When choosing a variant, use the existence of the bang as an opportunity to ask yourself if you might really want the safer version.

  • When reading code with a bang variant, assume the author assessed the risk/failure modes in play, and chose the bang variant for some hopefully evident and important reason.

Not much more to it than that! It’s mostly a convention for developers to communicate a decision of caution and careful thought across time and space.

The only real rule is that there shouldn’t be a bang function without a non-bang equivalent. The bang doesn’t represent danger so much as an important decision made with intent, so it must be something that you decided to do in contrast to a more benign option.

— All posts loaded —

Where Next? Top

Trending in Questions Top

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
roeland
Kia ora, We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
rahultumpala
Hello, I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
wintermeyer
There are three potential reasons for members of this forum to have a look at https://vutuv.de You are tired or annoyed of LinkedIn. Yo...
New

We're in Beta

About us Mission Statement