4 ms·
If it's an actual, standards adherent implementation of Go, nobody should a shit what you call it. If it actually changes the language spec, then you would have
by MaxfordAndSons 7y ago
If it's an actual, standards adherent implementation of Go, nobody should a shit what you call it. If it actually changes the language spec, then you would have to rename it for legal reason, but you should also want to rename it - unless it's a backwards compatible superset of the language, you wouldn't want people to think it's YAGC and just feed it their vanilla Go code and be surprised when it doesn't work.
- badsectoracula 7y agoHow does the adherence to Go's spec of a compiler affects its legality with regards to the compiler's name? And why is that an exception if it is a backwards compatible superset when a new version of the "real" Go could come out with new features that are incompatible with the extensions (thus rendering the previously compatible superset now incompatible and presumable illegal)?
- MaxfordAndSons 7y agoThe point I'm trying to make is there's a difference between re-implementing the language and forking it, is there not?