News for hackers. Stuff that matters.

A comment on Nim 2.0.0 RC2. Parent comment

Re:Nim 2.0.0 RC2 by v3ss0n on Friday March 31, 2023 @12:51PM (#35389816)
The main problem is people afraid about Style Insensitivity it enables by default .
[ Parent | on HN ]
Re:Nim 2.0.0 RC2 by elcritch on Friday March 31, 2023 @01:25PM (#35390187)
Its set to produce a compiler "Warning" by default now.
[ Parent | on HN ]
Re:Nim 2.0.0 RC2 by j-james on Friday March 31, 2023 @03:07PM (#35391842)
(for inconsistent usage)

As background, style insensitivity was introduced so that codebases can use a consistent camelCase or snake_case regardless of the style used by upstream libraries.

[ Parent | on HN ]
Re:Nim 2.0.0 RC2 by girvo on Monday April 03, 2023 @03:15AM (#35419675)
Which as an aside, makes writing and using C bindings so lovely.
[ Parent | on HN ]
Re:Nim 2.0.0 RC2 by j-james on Tuesday April 04, 2023 @09:25PM (#35448064)
Well, maybe not writing. Occasionally low-level C libraries - especially those that deal with keyboard input - decide to provide identifiers differing only in case... There's a WIP RFC for providing a way to deal with identifiers that need to be verbatium by surrounding them with backticks, though.

https://github.com/nim-lang/RFCs/issues/477

[ Parent | on HN ]