News for hackers. Stuff that matters.

A comment on Why Go and Not Rust?. Parent comment

Re:Why Go and Not Rust? by je42 on Tuesday September 17, 2019 @12:39AM (#20991617)
what's the alternative ? using an "untyped" variable ?

but then you loose type checking and some people don't like to loose type checking...

[ Parent | on HN ]
Re:Why Go and Not Rust? by KptMarchewa on Tuesday September 17, 2019 @07:46AM (#20993842)
Do not use patterns that require you to write code like that.
[ Parent | on HN ]
Re:Why Go and Not Rust? by Thiez on Tuesday September 17, 2019 @12:22PM (#20997015)
You never have cases where you have a list of lists? Or do you introduce a pointless wrapper type for the inner lists to "hide" the generics?
[ Parent | on HN ]
Re:Why Go and Not Rust? by ratww on Tuesday September 17, 2019 @11:39AM (#20996516)
That's the answer for me.

The problem in those cases always the abuse of often obsolete OOP patterns and misnamed classes.

[ Parent | on HN ]
Re:Why Go and Not Rust? by KirinDave on Tuesday September 17, 2019 @11:01AM (#20995951)
Or use type aliases that are helpful.
[ Parent | on HN ]