>> Anywhere that accepts an Operation Enum type will just as happily accept an int.
>Well, this is simply not true.
As comment above [1] pointed out `printOperation(2)` is still valid.
>Well, this is simply not true.
As comment above [1] pointed out `printOperation(2)` is still valid.
My understanding is that on a practical level, these kinds of issues arise from misusing types (or not caring about them) and naively putting variables of one type into the function that expects another. Examples with number constants typed in manually do not hold ground.