News for hackers. Stuff that matters.
Re:Nim 2.0.0 RC2 by pa7x1 on Friday March 31, 2023 @08:40AM (#35386207)
The only situation I can imagine this causing a problem in your codebase is if you intentionally want to mix camelCase and snake_case in your codebase and these 2 meaning different things. So if you don't enforce in your codebase a specific code style practice and you would like someFunction and some_function to coexist and mean different things, then yes. Nim's approach is problematic for you.

If you enforce a code style or, if you don't but you would convene that someFunction and some_function should mean the same thing in your codebase. Then nim's approach should be transparent to you.

Re:Nim 2.0.0 RC2 by overthrow on Friday March 31, 2023 @08:46AM (#35386280)
It also makes it a bit harder to grep a codebase. If you're on a team of 10 devs someone could have accidentally forgotten an underscore sometime last year. So you can't just grep for 'ready_for_upload', you have to use 'ready_?for_?upload'
Re:Nim 2.0.0 RC2 by pa7x1 on Friday March 31, 2023 @08:51AM (#35386361)
This is a valid observation.

I suspect, in practice, almost everyone follows the sane approach of enforcing a code style in your codebase. I think what usually gets lost when this is brought up is that the point of this code style insensitivity is not to encourage you go to crazy and mix and match it in your projects. It's so external dependencies don't have to infect your codebase. So you can actually apply a consistent code style within your project.

Re:Nim 2.0.0 RC2 by planetis on Friday March 31, 2023 @09:00AM (#35386471)
There are warnings raised by default, like this:

test.nim(2, 8) Hint: 'myvar' should be: 'myVar' [var declared in test.nim(1, 7)] [Name]

Re:Nim 2.0.0 RC2 by cardanome on Friday March 31, 2023 @08:51AM (#35386359)
Again, not if you enforce a code style which nearly always should in a professional context.

Such a mistakes is easy for a linter to pick up on so that the code would never be merged in the first place.

Re:Nim 2.0.0 RC2 by overthrow on Friday March 31, 2023 @08:57AM (#35386429)
How does the linter treat 'get_file_system' and 'get_filesystem'? Which one would be flagged as an error?
Re:Nim 2.0.0 RC2 by ptramo on Friday March 31, 2023 @10:14AM (#35387461)
The one that doesn't match the declaration.
Re:Nim 2.0.0 RC2 by overthrow on Friday March 31, 2023 @10:43AM (#35387883)
A parent comment says:

> It's so external dependencies don't have to infect your codebase. So you can actually apply a consistent code style within your project.

Say an external dependency has a declaration called 'getFileSystem', and in my Nim codebase I refer to it as 'get_file_system', but last year someone accidentally committed 'get_filesystem'. In this case neither usage matches the declaration. Does the linter flag both spellings because they don't match 'getFileSystem'?

EDIT: And what about reflection? If someone wrote `newCall("get_filesystem")`, will the linter fix that usage too?

Re:Nim 2.0.0 RC2 by darthrupert on Friday March 31, 2023 @08:52AM (#35386364)
I think there was a flag that allows you to turn bad style in identifiers into compile errors. It isn't but imho should be on by default.

edit --styleCheck:error perhaps?

Re:Nim 2.0.0 RC2 by michaelsbradley on Friday March 31, 2023 @08:48AM (#35386303)
Use nimgrep?
Re:Nim 2.0.0 RC2 by Nullabillity on Friday March 31, 2023 @08:59AM (#35386464)
Ripgrep is already integrated into my editor and muscle memory. Nimgrep is just yet another special case tool that only exists because Nim decided to spend its weirdness budget on inconsequential nonsense.
Re:Nim 2.0.0 RC2 by xigoi on Friday March 31, 2023 @12:17PM (#35389347)
The “weirdness budget” concept is nonsense. Are you saying that programming languages should do only some things right?
Re:Nim 2.0.0 RC2 by overthrow on Friday March 31, 2023 @08:54AM (#35386391)
Can you integrate that into an IDE? In many IDEs, if you hit ctrl-shift-f, it will search the project for the selected text with just one keystroke. Can vscode be made to Do The Right Thing for Nim without extra fiddling on every search?
Re:Nim 2.0.0 RC2 by michaelsbradley on Friday March 31, 2023 @09:00AM (#35386466)
Good question, but I don't know the answer (yet) because I don't use vscode, sorry.
Re:Nim 2.0.0 RC2 by Manabu-eo on Tuesday April 04, 2023 @08:23PM (#35447612)
Your Nim project will be in a consistent casing, otherwise the compiler will be warning you about inconsistent spelling. Regular Ctrl-shift-f will work just fine.
Re:Nim 2.0.0 RC2 by planetis on Friday March 31, 2023 @09:05AM (#35386533)
@Nullabillity The only nonsense we are dealing with constantly is opinions of people who haven't ever bothered to use this feature before declaring it "inconsequential nonsense".
Re:Nim 2.0.0 RC2 by Nullabillity on Friday March 31, 2023 @09:15AM (#35386665)
whodoesthissocalledfeaturehelpandwhatkindofcodedoesitencourage

iwouldnotwanttoworkinanenvironmentwherethiswasaseriousproblemthatpeoplethoughtneededsolving

Re:Nim 2.0.0 RC2 by planetis on Friday March 31, 2023 @10:41AM (#35387872)
Very mature, congratulations! Naming has nothing to do with style insensitivity. You can write M_ya_wse_s_omEv_ar in any language, yes? Proof that you don't understand what you're arguing about.
Re:Nim 2.0.0 RC2 by Nullabillity on Friday March 31, 2023 @10:55AM (#35388060)
> You can write M_ya_wse_s_omEv_ar in any language, yes?

Yes? That doesn't mean that we should add features that encourage that kind of confusion. Especially not when they, again, help nobody and bring no actual benefit.

Re:Nim 2.0.0 RC2 by stefncb on Friday March 31, 2023 @11:39AM (#35388762)
If anything, it encourages a consistent style, since you don't have to use whatever style your dependency uses.

Also, if you work with people that name things like that, it's not really Nim's fault?

Re:Nim 2.0.0 RC2 by Nullabillity on Friday March 31, 2023 @12:49PM (#35389774)
Somehow pretty much every other ecosystem can just pick one style and stick to it, negating the problem entirely.

I have never come across a Rust project that didn't use snake_case, or a Java project that didn't use camelCase.

Re:Nim 2.0.0 RC2 by monetus on Friday March 31, 2023 @11:24AM (#35388501)
(Not who you responed to)

Just to argue against there being no benefit, I have a cognitive impairment that occasionally puts me in an altered state, a delirium to varying degrees. camelCase is much more difficult to read at that point, so I can get confused ridiculously easily. I tend leave a bunch of comments and then step away, but sometimes I can work well through it; things like horrendous variable names/regexs will throw me. I default to snake_case but compile over when I share the code.

This is my unique situation and predilection to being able to read one form more easily than another, but it does indeed help me.

Re:Nim 2.0.0 RC2 by Nullabillity on Friday March 31, 2023 @12:47PM (#35389755)
That's understandable, but doesn't that cause the same issues when reading documentation or third-party code?
Re:Nim 2.0.0 RC2 by monetus on Friday March 31, 2023 @02:47PM (#35391514)
I can back away from those while leaving the tabs open and be not too confused coming back, not having temporarily broken them. When I'm in the middle of refactoring especially though, getting a seizure and trying to back away without jumbling the house of cards is a lot easier with whatever pattern recognition I have around snake_case.

Edit: curious, have a preference besides consistency for cases?

Re:Nim 2.0.0 RC2 by v3ss0n on Friday March 31, 2023 @12:56PM (#35389885)
Why would someone change its tooling because of a particular Language ?
Re:Nim 2.0.0 RC2 by Manabu-eo on Tuesday April 04, 2023 @08:18PM (#35447583)
Do you use it regularly? I don't, and I don't have any problem finding what I need with regular ctrl+F in Nim, because Nim projects are internally consistent in terms of style, with the compiler helping enforcing it with `-styleCheck`.

So don't bring up nimgrep like it's a necessity when it's more of a last resort tool nowadays. You will be just attracting flaming.

Re:Nim 2.0.0 RC2 by frou_dh on Friday March 31, 2023 @09:45AM (#35387073)
Tooling (In this case, "Find References") should understand language semantics. Not that I think that this specific feature of Nim is particularly appealing, but pandering to 1970s stone-age tooling forever is just sad.
Re:Nim 2.0.0 RC2 by mtinkerhess on Friday March 31, 2023 @10:23AM (#35387600)
You don't always get to pick your tools. If you're using GitHub, ctrl+F should find what you're looking for.
Re:Nim 2.0.0 RC2 by xxpor on Friday March 31, 2023 @11:48AM (#35388902)
As a C programmer where the codebases I work on have never adopted any sort of style enforcement: sounds like a normal day to me.
Re:Nim 2.0.0 RC2 by Nullabillity on Friday March 31, 2023 @09:11AM (#35386611)
It would be one thing (but still a weird feature that calls the rest of their decision making into question) if it normalized fooBar into foo_bar (or the opposite). But that's not what it actually does, it normalizes both into foobar, which introduces new ambiguities. In fact, you can often end up with the opposite meaning! For example, a few Swedish examples:

- hand tvättas (wash your hands) != handtvättas (wash by hand)

- sjuk gymnast (sick gymnast) != sjukgymnast (physical therapist)

- sjuk sköterska (sick nurse) != sjuksköterska (hospital nurse)

- lång hårig (tall and hairy) != långhårig (long-haired)

- sjö nära tomt (lake near a house) != sjönära tomt (house near a lake)

Re:Nim 2.0.0 RC2 by tokai on Friday March 31, 2023 @09:29AM (#35386852)
Natural language compound words has no bearing on a discussion on Nim. It makes even less sense to use a language full of compound words like Swedish, when Nim is written in English - a language where compound words are less common and flexible.
Re:Nim 2.0.0 RC2 by Nullabillity on Friday March 31, 2023 @09:31AM (#35386881)
Nim itself, or the code bases written in Nim?
Re:Nim 2.0.0 RC2 by Tommstein on Friday March 31, 2023 @07:58PM (#35395434)
Nim forces you to use English identifiers?
Re:Nim 2.0.0 RC2 by netbioserror on Friday March 31, 2023 @09:15AM (#35386661)
These examples apply to a codebase...how?
Re:Nim 2.0.0 RC2 by konart on Friday March 31, 2023 @09:31AM (#35386896)
Method\variables naming?
Re:Nim 2.0.0 RC2 by fredrikholm on Friday March 31, 2023 @09:39AM (#35387003)
I'm a Swede working in Sweden and Norway, and I've never seen any code written in a Scandinavian language (thank god).
Re:Nim 2.0.0 RC2 by dieortin on Friday March 31, 2023 @12:04PM (#35389142)
Variables are usually named after things, so of course they apply to a codebase. How would they not apply?
Re:Nim 2.0.0 RC2 by WesolyKubeczek on Friday March 31, 2023 @09:16AM (#35386681)
Another situation is when you have to interface with some other language that doesn't have this feature and where nameLikeThis and name_like_this both exist and mean different things. Thus requiring you to work it around with a third naming convention.

Here's one illustration: https://github.com/nim-lang/RFCs/issues/456#issuecomment-111...

We have partial case-insensitivity in PHP. Can't say I'm very fond of it, but I'm ambivalent as long as it's not abused.

Re:Nim 2.0.0 RC2 by xigoi on Friday March 31, 2023 @12:20PM (#35389376)
You should rename foreign identifiers anyway. C names are usually very cryptic.
Re:Nim 2.0.0 RC2 by WesolyKubeczek on Friday March 31, 2023 @06:18PM (#35394463)
This has a drawback that when reading the original documentation, not only do you have to mentally translate the code examples into your target language, but also translate the identifiers too.

And "C names are usually very cryptic" is plain false, unless you talk about APIs coming from the ages and compilers where all identifiers had to be 8 characters or fewer in length.

Re:Nim 2.0.0 RC2 by nerdponx on Friday March 31, 2023 @09:35AM (#35386950)
* * *
Re:Nim 2.0.0 RC2 by xigoi on Friday March 31, 2023 @12:19PM (#35389363)
> This is literally idiomatic Python style! Classes are TitleCase and everything else is snake_case.

And Nim does distinguish between those.

> I've written names like "fooBar_prev"

That's disgusting.

Re:Nim 2.0.0 RC2 by v3ss0n on Friday March 31, 2023 @12:53PM (#35389839)
This is done a lot in Python Libraries the module with lower_case and class name with TitleCase . In Nim's Case (No Pun Intended) it is a fatal mistake.
Re:Nim 2.0.0 RC2 by dsrw on Friday March 31, 2023 @02:11PM (#35390963)
This particular example isn't actually an issue in Nim. The first letter of a nim identifier is case sensitive, so while `my_thing` and `myThing` are normalized to the same name, `my_thing` and `MyThing` are different.
Re:Nim 2.0.0 RC2 by 000ooo000 on Friday March 31, 2023 @08:50PM (#35395826)
I'm not sure I understand the rationale of it if using a consistent naming approach (best practice) renders it transparent, and compiler warnings alert you to instances where one is using e.g. my_var and myVar. Seems like the capability is there but the typical advice and compiler both warn against taking advantage of it. Just seems like a footgun to me. What am I missing?
Re:Nim 2.0.0 RC2 by Manabu-eo on Tuesday April 04, 2023 @08:25PM (#35447631)
It's there to allow you to have a consistent naming approach inside your project, regardless of the naming approach of the libraries you are using.