As others pointed out, this was not true when ‘enums’ were added, but still the Java compiler has always supported compiling using old version constructs. In the case of enums it was binary compatible.
I think Ian’s proposal on the comment build flag to specify the language version is a good one. I think you might need to also be able to specify the language version in the mod file for legacy modules you don’t want to edit/maintain (as they wouldn’t have the per file comments either). > On Oct 27, 2018, at 5:29 PM, hay <habibalyou...@gmail.com> wrote: > > "To this day, you can take a “binary” written for Java 1.0 and it will run > under the latest JRE. You can compile Java 1.0 source code with the latest > compiler. This is an amazing accomplishment that can’t be understated." > I've concern about this. This kind of guarantee might prevent needed changes > in the future version. In my opinion, backward compatibility guarantee by > major version is best approach. For Go 2 and Go 3 developers should change > their code if it breaks. > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com > <mailto:golang-nuts+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
