Mirror of forum.nim-lang.org

7219 :: Nim Lang requires a proper standard for coding

• v3ss3n (orginal) [2020-12-07T14:47:25+01:00] view original

  Nim is having a non-standard coding style : I am seeing various variable naming commonly

  • snake_case
  • camelCase

  And many others. Without picking a proper formatting , it will be hard for contributors and users .

---

• Araq (orginal) [2020-12-07T14:53:56+01:00] view original

  We have a style guide and tooling to enforce it, nim --styleCheck:error. See also https://nim-lang.org/docs/nep1.html

---

• juancarlospaco (orginal) [2020-12-07T15:08:07+01:00] view original

  Let GitHub work for you https://github.com/juancarlospaco/nimpretty-action#nimpretty-action

---

• Stefan_Salewski (orginal) [2020-12-07T15:35:05+01:00] view original

  Let GitHub work for you

  Can your github version of nimpretty do real work? My local one does generally only splitting long lines, what I do not really like, so I pass maxLineLength parameter set to 130, and then it does nothing at all. I does not convert snakes to camels.

---

• Araq (orginal) [2020-12-07T15:38:42+01:00] view original

  It does not convert snakes to camels.

  That's not its job, no other comparable tool (gofmt, clang-tidy, etc) does that either.

---

• miran (orginal) [2020-12-07T16:30:24+01:00] view original

  and then it does nothing at all

  Congrats, you're writing pretty nim code by yourself.

---

• miran (orginal) [2020-12-07T16:32:43+01:00] view original

  And many others.

  Can you name/show at least three of those many others?

---