3 ms·
It kind of sounds like you're looking for technical means by which to "signal to others". In that case, perhaps some documentation (for other contributors/maint
by usefulcat 9y ago
It kind of sounds like you're looking for technical means by which to "signal to others". In that case, perhaps some documentation (for other contributors/maintainers) could be of use?
Beyond that I'm not sure what to suggest. The problem is that even if you have a Really Good Reason for what might otherwise appear to be a bit of gratuitous incompatibility, it's rather unlikely that others will figure out what that reason is without some explanation. IME anyway.
- blackflame7000 9y agoDocumentation is only good if people read it... which most developers don't. If someone tried to make a class called string in my module, they would receive immediate feed back from the compiler that there are now multiple definitions of string which should tell them that they are creating another copy of something that already exists. Nevertheless, I'll concede that its not the best way to go about things. But it is something you can do and I wanted to highlight a case of why a "Never do This" feature is even allowed in the first place.