How generics are implemented in Go 1.18

Re:How generics are implemented in Go 1.18 by shadowgovt on Tuesday March 01, 2022 @09:22PM (#30522908)

Computers seem to have caught up. The Java stack is the slowest one I regularly use (though it does support a certain amount of hot-recompile that other toolchains I use don't or can't), but it's never just crashed because it can't find room to store all those bytecode files.

[ Parent | on HN ]

Re:How generics are implemented in Go 1.18 by vips7L on Tuesday March 01, 2022 @10:56PM (#30523474)

I’ve compiled projects with javac, scalac, g++, gcc, and dmd. Javac is faster than all of them.

[ Parent | on HN ]

Re:How generics are implemented in Go 1.18 by pkolaczk on Wednesday March 02, 2022 @04:32AM (#30525491)

javac doesn't have to generate optimized machine code, which saves it a lot of time. But you pay the price incrementally in all those slow startups of java apps.

[ Parent | on HN ]

Re:How generics are implemented in Go 1.18 by pjmlp on Wednesday March 02, 2022 @08:06AM (#30526878)

Only if stuck in Java 8, those of us in modern Java use JIT caches with PGO feedback.

[ Parent | on HN ]