From 4bf44ca47f68869eab53cc0050b613dda0db8e1f Mon Sep 17 00:00:00 2001 From: c-blake Date: Thu, 19 Mar 2026 02:39:18 -0400 Subject: [PATCH] See discussion at https://github.com/nim-lang/Nim/pull/25602 . (#25612) It seems in dispute whether changes to code induced to avoid this new warning firing are worthwhile. Until either the analyzer is better or a palatable way to adjust stdlib code not warn is found, verbosity=1 should not include the warning. Possibly higher levels, too, but this PR is conservative and only takes it out at the 2->1 transition. --- compiler/lineinfos.nim | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compiler/lineinfos.nim b/compiler/lineinfos.nim index dc8708c3e4..bb3f519535 100644 --- a/compiler/lineinfos.nim +++ b/compiler/lineinfos.nim @@ -266,7 +266,7 @@ proc computeNotesVerbosity(): array[0..3, TNoteKinds] = result = default(array[0..3, TNoteKinds]) result[3] = {low(TNoteKind)..high(TNoteKind)} - {warnObservableStores, warnResultUsed, warnAnyEnumConv, warnBareExcept, warnStdPrefix, warnSystemRangeConversion} result[2] = result[3] - {hintStackTrace, hintExtendedContext, hintDeclaredLoc, hintProcessingStmt} - result[1] = result[2] - {warnProveField, warnProveIndex, + result[1] = result[2] - {warnImplicitRangeConversion, warnProveField, warnProveIndex, warnGcUnsafe, hintPath, hintDependency, hintCodeBegin, hintCodeEnd, hintSource, hintGlobalVar, hintGCStats, hintMsgOrigin, hintPerformance} result[0] = result[1] - {hintSuccessX, hintSuccess, hintConf,