From 59e1e430e22f311d1614fe81a54ec65a533cc55f Mon Sep 17 00:00:00 2001 From: tersec Date: Thu, 15 Jun 2023 09:33:32 +0000 Subject: [PATCH] Nim 1.2 isn't current anymore, and --styleCheck:error is generally feasible --- src/formatting.naming.md | 2 +- src/formatting.style.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/formatting.naming.md b/src/formatting.naming.md index 32d3cb5..5619b48 100644 --- a/src/formatting.naming.md +++ b/src/formatting.naming.md @@ -2,7 +2,7 @@ Always use the same identifier style (case, underscores) as the declaration. -Enable `--styleCheck:usages`. +Enable `--styleCheck:usages`, and, where feasible, `--styleCheck:error`. * `Ref` for `ref object` types, which have surprising semantics * `type XxxRef = ref Xxx` diff --git a/src/formatting.style.md b/src/formatting.style.md index 6b1a217..292143e 100644 --- a/src/formatting.style.md +++ b/src/formatting.style.md @@ -22,8 +22,8 @@ func someLongFunctinName( ### Practical notes -* We do not use `nimpretty` - as of writing (nim 1.2), it is not stable enough for daily use: +* We do not use `nimpretty` - as of writing (Nim 1.6), it is not stable enough for daily use: * Can break working code * Naive formatting algorithm * We do not make use of Nim's "flexible" identifier names - all uses of an identifier should match the declaration in capitalization and underscores - * Enable `--styleCheck:usages` + * Enable `--styleCheck:usages` and, where feasible, `--styleCheck:error`