News for hackers. Stuff that matters.

A comment on Gopher Wrangling. Effective error handling in Go. Parent comment

Re:Gopher Wrangling. Effective error handling in Go by kaba0 on Tuesday June 20, 2023 @06:52AM (#36402196)
You have conveniently left out types from go’s list.. with those removed it is hardly longer, and as has been shown (case-sensitive identifiers), not all language complexity lives within keywords.
[ Parent | on HN ]
Re:Gopher Wrangling. Effective error handling in Go by preseinger on Tuesday June 20, 2023 @07:47AM (#36402680)
the parent's point was to compare the set of reserved keywords in the two languages

types do not enter the discussion

[ Parent | on HN ]
Re:Gopher Wrangling. Effective error handling in Go by kaba0 on Tuesday June 20, 2023 @11:45AM (#36405743)
They do if 1/3 of java’s keywords are there due to types.
[ Parent | on HN ]
Re:Gopher Wrangling. Effective error handling in Go by preseinger on Tuesday June 20, 2023 @12:19PM (#36406370)
some keywords are types, but not all types are keywords, right?

like, it's not as if the go type `float64` is also a go keyword

but i guess the java type `byte` is a java keyword? according to https://docs.oracle.com/javase/tutorial/java/nutsandbolts/_k...

[ Parent | on HN ]
Re:Gopher Wrangling. Effective error handling in Go by adezxc on Tuesday June 20, 2023 @08:13AM (#36402918)
https://go.dev/play/p/71I57QCycTr This works, so how exactly did I leave them out?
[ Parent | on HN ]