Defining operations using protocols

just keep in mind that 1) the changes are lexically scoped. That’s a good thing ™ since it contains the statefulness of potentially confusing conventions and 2) the changes are strictly opt-in, you can’t enforce it globally (AFAIK) and 3) they’re not composable. If someone else has a library that does that you can’t use it in the same code block as yours.

Thank you. The code in your link clarified many other questions I already had.

Agreed. Another approach is to limit operator overrides to a macro call so that outside of it things continue to work as usual. Here’s a proof-of-concept I did for Decimal [1] a while ago:

iex> require DecimalEval
iex> a = 1
iex> b = 2
iex> DecimalEval.eval (a + b) * "3.0"
#Decimal<9.0>

[1] GitHub - wojtekmach/decimal_eval · GitHub

It’s possible. You can un-import from Kernel and re-import. For example:

https://github.com/ityonemo/annex/blob/experimental/test/experimental/elixir_tensor_test.exs

However, it’s somewhat discouraged.

Please use triple backtick blocks to format code: Markdown cheat sheet.

And no, Erlang and Elixir do not allow overriding of operators per se. You are much better off using function names like add, sub, mul, div, mod etc.