I don’t get “functionally added”. They exists as a part of language. They are named “special” for purpose.
Special forms are the basic building blocks of Elixir, and therefore cannot be overridden by the developer.
It’s like you want to replace foundations of house and expect that nothing bad would happen. Special forms are not even macros like the ones you are writing. They are expanded by compiler and this is a completely different topic.
wait, wait
Non-unary operators like a = b have always 2 arity and you wrote about different arity. How do you see 3 or 4-arity operator?
The problem is that you would need to describe that weird behaviour to all developers using you library. The inspecting is only in examples. Most probably you would not log them and that would be extremely confusing.
The good practice is to write a code and be able to describe what it does even if you stop touching it for let’s say 6 months. In your case the developer would need to remind which macros are overriding operator and in which order. Now think that you decide to change behaviour of your library and this time you want to take operator from first macro. If so would happen nobody maybe except maintainers would follow the whole process.
Hiding everything is not always the best way and in some cases it may be seen as a bad practice.
