Mirror of forum.nim-lang.org

8602 :: Nim v1.2.14 released

• miran (orginal) [2021-11-08T10:35:25+01:00] view original

  For our users who are still using Nim 1.2, we have released a 7th patch release — Nim 1.2.14. It contains the following changes compared to the previous patch release:

  • Fixed "Compiler warning on mismatching case/spelling" (#15848)
  • Fixed "[CI] tests/async/tioselectors.nim flaky test for freebsd + OSX CI" (#13166)
  • Fixed "Accessing an empty array sometimes works" (#18643)
  • Fixed "parseutils.parseFloat for e.g. 9.123456789012345+ returns a result that is 1e15 too big" (#18702)
  • Fixed "Asyncdispatch+stackTraceOverride: premature collection" (#18039)
  • Fixed "Buffer-overrun bug in net" (#17728)
  • Feature: "the compiler can warn when you use the implicit 'result' variable" (#17988)
  • Feature: "allow converting static vars to openArray" (#19049)

  You can download Nim 1.2.14 from our nightly release or from our website under "Install previous versions" on this page.

---

• brainproxy (orginal) [2021-12-03T19:33:13+01:00] view original

  Why isn't there a corresponding v1.2.14 tag in the official GitHub repo?

---

• miran (orginal) [2021-12-03T21:06:21+01:00] view original

  Why isn't there a corresponding v1.2.14 tag in the official GitHub repo?

  I guess I forgot to push it. It should be there now.

  Thanks for notifying us, and sorry about this mishap.

---

• didlybom (orginal) [2021-12-03T22:34:09+01:00] view original

  I’m curious. Is there a big incompatibility between 1.2 and later versions?

---

• arnetheduck (orginal) [2021-12-04T19:10:51+01:00] view original

  It is possible to write code that works with both 1.2 and 1.6, but in our 1.2 codebase, practically every library needs some sort of update to compile (we haven't gotten as far as testing actually running it) - 1.4 unfortunately contained many breaking changes - with 1.6, significant work has been done to reduce the surface area of breaking changes with new stability policies, which is great news!

---

• arnetheduck (orginal) [2021-12-05T15:38:36+01:00] view original

  Actually, for anyone looking for ideas on upgrade paths between Nim versions, here's a writeup of what we're doing: https://discuss.status.im/t/the-road-to-nim-1-6/2305

  In particular, it involves testing with multiple nim releases, and recognizing that when developing libraries, a library is more useful the more versions of its dependencies that it supports (and tests) - this means that the more generally useful the library, the better it is if it supports older Nim versions - conversely, when developing applications, you want to support only one version of everything and have control over what you upgrade, at when.

---