Expectations for generics in Go 1.18

Re:Expectations for generics in Go 1.18 by dagmx on Wednesday October 27, 2021 @10:50PM (#29021812)

I'm actually curious if Go would normalize the characters AND if it had used angle bracketd, and make those equivalent to angle brackets? Would he then not have to even change his code?

I guess that's a lot of ifs/ands but it's interesting that one could have future proofed their code if their bet on syntax paid off

[ Parent | on HN ]

Re:Expectations for generics in Go 1.18 by jchw on Wednesday October 27, 2021 @11:12PM (#29021950)

They're semantically different characters and Go supports multilingual identifiers, so I would not expect normalization to impact this. At most I would expect normalization to simply deal with ordering combining marks and standardizing on composed or decomposed forms of characters (where applicable.)

[ Parent | on HN ]

Re:Expectations for generics in Go 1.18 by nitrogen on Thursday October 28, 2021 @02:37AM (#29023073)

This got me curious what I'd read about domain names and visual normalization of Unicode, and found this: http://www.unicode.org/Public/security/revision-05/confusabl...

It might be useful for editors and compilers to check for tricky Unicode (lookalikes for common characters, atypical changes in direction, invisible spaces or other formatting control codes, etc.) in this era of copy/paste coding.

[ Parent | on HN ]

Re:Expectations for generics in Go 1.18 by tialaramex on Thursday October 28, 2021 @03:05AM (#29023253)

I believe Rust will warn you if your non-ASCII identifiers are potentially confusing based on this list.

[ Parent | on HN ]