4 ms·
I like this idea. The problem I see is when you have different, but equally valid implementations. In this case, it would make sense to back the name up with t
by joeyespo 15y ago
I like this idea. The problem I see is when you have different, but equally valid implementations.
In this case, it would make sense to back the name up with the developer/company name. But with no further decoration, as discussed. That way, it's clear which function implementation you're referring to. You can still have the mainstream (popular? chosen by the project's team?) implementations be referenced by function name alone. Any other implementations would need the dev/company name. That way you can have different parts of the project still able to reference different implementations of the same function.
The alternative would be to decorate the function with the implementation detail. And I think that's going against the simplicity he's after. Worse still is you'd still need to know you'll be supporting multiple implementations up front.