does Go not support overloading of methods and operators? Method dispatch is simpli fi ed if it doesn't need to do type matching as well. Experience with other languages told us that having a variety of methods with the same name but di ff erent signatures was occasionally useful but that it could also be confusing and fragile in practice. Matching only by name and requiring consistency in the types was a major simplifying decision in Go's type system. Regarding operator overloading, it seems more a convenience than an absolute requirement. Again, things are simpler without it. https://go.dev/doc/faq#overloading
'Software Quality Metrics to Identify Risk'[ 8 ] for the Department of Homeland Security, Tom McCabe introduces the following categorisation to interpret cyclomatic complexity: • 1 - 10 Simple procedure, little risk • 1 1 - 20 More complex, moderate risk • 2 1 - 50 Complex, high risk • > 50 Untestable code, very high risk 45 https://en.wikipedia.org/wiki/Cyclomatic_complexity