News for hackers. Stuff that matters.
Re:Generics in Go with Ian Lance Taylor (2019) by hinkley on Tuesday February 18, 2020 @07:11PM (#22361823)
I suspect the problem is that Generics bring you face to face with the Liskov Substitution Principle. For most of us it's just a good idea, and then you try to do generics and all of a sudden it begins to become the law.

So you try to layer it onto a language like Java and you discover that an ArrayList of Integer is not interchangeable with an ArrayList of Number because you can stick a Double in one of them and blow up everyone expecting only whole numbers.

I've long suspected that you either have to put Generics in at the beginning or prepare for decades of complaints about your workarounds. And getting stuck in committee for a very, very, very long time.

Re:Generics in Go with Ian Lance Taylor (2019) by lazulicurio on Tuesday February 18, 2020 @07:42PM (#22361992)
> So [...] you discover that an ArrayList of Integer is not interchangeable with an ArrayList of Number because you can stick a Double in one of them and blow up everyone expecting only whole numbers.

Is this really an issue with Java's type system though? If you get an ArrayList<Number> and you assume that it contains only whole numbers, that's on you.

FWIW, my personal opinion is that erasure is better than templated generics for most use cases. Even when it comes to performance: a good JIT should be able to specialize generic code that end up on a hot path. Erasure does cause some issues with reflection and value types, but I think that it provides a better foundation to start from when designing a type system.

Then again, I am quite a fan of Rust's generics and dyn/impl {Trait}. Might be worth doing something similar where you have two separate generic systems: one for boxed values, and one for unboxed values.

Re:Generics in Go with Ian Lance Taylor (2019) by esrauch on Tuesday February 18, 2020 @09:11PM (#22362495)
> Is this really an issue with Java's type system though? If you get an ArrayList<Number> and you assume that it contains only whole numbers, that's on you.

The point is that you have an List<Integer> are you allowed to call a function that takes an List<Number>? The answer is effectively "yes it should be allowed" if its not mutating the List (all Integers can be safely read as Numbers) but no if the List is mutable (you can't handle the fact that it might insert a non-Integer number into the Integer-only List).

Re:Generics in Go with Ian Lance Taylor (2019) by joshuamorton on Tuesday February 18, 2020 @10:55PM (#22362923)
This is less LSP and more the co/contravariance of container types, which is its own special hell.
Re:Generics in Go with Ian Lance Taylor (2019) by LessDmesg on Wednesday February 19, 2020 @01:18AM (#22363463)
The hell stems from inheritance, which is just syntactic sugar over composition. And a very unhealthy kind of sugar as that: problems with co- and contravariance, problems with copying, the need for redundant type declarations. And inheritance doesn't guarantee autofulfillment of the Liskov principle, either. One might even wonder why inheritance is needed at all in a language. Go and Rust are certainly fine without it.
Re:Generics in Go with Ian Lance Taylor (2019) by hinkley on Wednesday February 19, 2020 @01:27PM (#22368425)
One of the humblest smart guys I worked with years ago would try to convince me over lunch that the Next Big Language would have syntactic sugar to make composition as easy as inheritance. I think in part because I had intimated that I was trying to create a language (narrator: he didn't. It went nowhere)

There are a couple languages that have added something like this in the interim, but nobody seems to have made it an idiomatic thing. Which is a shame, because I still think I might like to work in the world he dreamed up.

You get a little more composition in languages like NodeJS for the very pragmatic reason that inheritance, at least historically, was not seamless and hence had a high degree of friction.

Re:Generics in Go with Ian Lance Taylor (2019) by pjmlp on Thursday February 20, 2020 @02:53AM (#22373462)
Ah, just like VB did with COM....
Re:Generics in Go with Ian Lance Taylor (2019) by hinkley on Wednesday February 19, 2020 @04:32AM (#22364157)
With the possible exception of a couple of convenience methods, you can model collections (independently) as a source and sink for elements and avoid having to rely on variance at all. But we treat them as a storehouse of shared state... which ought to be our first warning that things are about to go sideways.

Lots of people get confused by variance. They shouldn’t, but insisting in what people should or shouldn’t do rather than working with how they are is a sure route to frustration.

Re:Generics in Go with Ian Lance Taylor (2019) by NovaX on Wednesday February 19, 2020 @12:30AM (#22363260)
It isn't a problem if you design an API by following the rules (PECS). Use wildcards for method parameters when this is the desired behavior. It is not hard to do things right.

https://howtodoinjava.com/java/generics/java-generics-what-i...

Re:Generics in Go with Ian Lance Taylor (2019) by yarg on Wednesday February 19, 2020 @03:34AM (#22363936)
void doThings(List<? extends Number> values){ ... }

This is catered for.

Re:Generics in Go with Ian Lance Taylor (2019) by apta on Thursday February 20, 2020 @03:47PM (#22378451)
> because you can stick a Double in one of them and blow up everyone expecting only whole numbers.

Generics in Java are invariant, so what you're describing will not work.