Nim version

[2-towns]

No description provided.

[2-towns]

I am trying to use the 2.0.12 version because it is not too big a jump (compared to 2.2.2). Moreover, the Nimbus build system switched to it one month ago, and this is the last patched version for 2.0.x.

But I am worried about Constantine, which dropped support for 1.6.12 and 2.0.x because it wasn't compiling... They still have a statement:

Hence we only test and officially support 2.2.0, though 99% of Constantine should work on older compilers.

So I will try with 2.0.12, and we will see...

[dryajov]

I think only 2.2.x were considered stable enough to make the jump. Can we confirm this with the nimbus team?

[dryajov]

Tagging @arnetheduck for some insights.

[arnetheduck]

Nimbus (and waku) use 2.0.x for now, with --mm:refc. 2.2 has not gone through nimbus' Q/A yet, last I checked there were some issues (cc @tersec). --mm:orc has not gone through Q/A in any nim version. 1.6 is EOL.

Regarding 2.2, if something works there but not in 2.0 and this is due to a bugfix (rather than some new feature), we usually investigate and negotiate a backport of the fix and a new 2.0.x release (I recommend all teams contribute to this process). The easiest way to do this is to report which bugfix needs backporting in the nim issue tracker.

[tersec]

Nimbus (and waku) use 2.0.x for now, with --mm:refc. 2.2 has not gone through nimbus' Q/A yet, last I checked there were some issues (cc @tersec). --mm:orc has not gone through Q/A in any nim version. 1.6 is EOL.

Nim v2.2.0 still has many issues which are fixed in v2.0.12 thanks to backports from devel by @narimiran including but not limited to:

• Regression from 2.0.8/version-2-0 to version-2-2/devel with Error: type mismatch with templates and generics nim-lang/Nim#24125
• Regression from v2.0.8 to v2.0.10/version-2-0/2.2/devel: Error: request to generate code for .compileTime proc: $ nim-lang/Nim#24228
• regression from v1.6.12: --styleCheck:error stops checking style for openArray nim-lang/Nim#24269
• Regression from v2.0.10 to 2.2/devel in const with cstring/string literal conversion: context: n.nim(2, 21) Error: type mismatch: got 'cstring' for '""' but expected 'string' nim-lang/Nim#24295
• With const c: cstring using literal string value from template, Error: type mismatch: got 'cstring' for '""' but expected 'string' nim-lang/Nim#24296
• error: redeclaration of ‘qX60gensym0_’ with no linkage with nested templates nim-lang/Nim#24338
• Error: VM problem: dest register is not set with const-bound proc nim-lang/Nim#24359
• SIGSEGV with nim c -c and nim e on macro w(): untyped = result = genSym(nskType) nim-lang/Nim#24379

This is because https://github.com/nim-lang/Nim/commits/version-2-2/ has not been updated in 2 months, while devel has fixed all of these.

Similarly, as a result of this lack of activity in the version-2-2 branch since v2.2.0 was released, it's unclear what Nim's release plans for 2.2.x are, while we can be fairly confident we can get fixes we need on 2.0.x.

So, yes, it indeed has not gone through the QA process. Going from v2.0.12 to v2.2.0 is a very lateral move at this point, with the downside of not being consistent with the rest of IFT.

The combination of known regressions in 2.2.0 vs 2.0.12 and the lack of any visible plan or schedule on which they might be fixed would encourage usage of v2.0.12 and updated v2.0.x versions until that situation is clarified.

I'd like to migrate Nimbus to v2.2.x when it's reasonable, but so far it does not look practical or reasonable.

Regarding 2.2, if something works there but not in 2.0 and this is due to a bugfix (rather than some new feature), we usually investigate and negotiate a backport of the fix and a new 2.0.x release (I recommend all teams contribute to this process). The easiest way to do this is to report which bugfix needs backporting in the nim issue tracker.

Indeed, and hopefully having identified one reason @mratsim dropped v2.0.x, we can get a backport for at least that much.

[dryajov]

Thanks! That clarifies it. @2-towns lets stick with the latest 2.0.x.