A Proposal for Package Versioning in Go

Re:A Proposal for Package Versioning in Go by pjmlp on Tuesday March 27, 2018 @08:46AM (#16687731)

There are also CLU, Ada, Modula-2, Modula-3, Eiffel, Sather, BETA as possible inspirations for implementing generics, all the way back to 1976 (CLU).

As for C#, people keep forgetting .NET always had a JIT/AOT compiler since version 1.0.

Just because not everyone bothers to sign their applications and call NGEN at installation time, it doesn't mean it isn't there.

Also Mono always supported AOT compilation, it is the way Xamarin works on iOS and the deployment story on Windows Store since it was introduced on Windows 8.

[ Parent | on HN ]

Re:A Proposal for Package Versioning in Go by ngrilly on Tuesday March 27, 2018 @11:16AM (#16689290)

I remember Mono with AOT compilation had some limitations regarding generics in the past, but maybe this has been solved since then.

[ Parent | on HN ]

Re:A Proposal for Package Versioning in Go by pjmlp on Tuesday March 27, 2018 @12:07PM (#16689839)

Yes Mono has some limitations, but it isn't 100% like the iOS Xamarin compiler.

http://www.mono-project.com/docs/advanced/aot/

In any case, a limited form of generics is better than not having any at all.

They don't need to provide a turing complete implementation of generics, even a basic one like CLU had would already be an improvement.

Using go generate feels like the old days, writing generic code in C and C++ with pre-processor tricks.

[ Parent | on HN ]

Re:A Proposal for Package Versioning in Go by ngrilly on Tuesday March 27, 2018 @12:27PM (#16690074)

I agree. I hope the Go team will tackle this issue, when they are done with dependency management.

[ Parent | on HN ]