Mirror of forum.nim-lang.org

9908 :: My Nim Development Progress Weekly

• ringabout (orginal) [2023-02-19T09:46:04+01:00] view original

  First of all, the Nim development follows The Roadmap 2023, which specifies what features might be implemented or removed in 2023. As we can see, completing incremental compilation and recursive module dependencies might be the most important tasks to be done in 2023. You might subscribe to the roadmap and write down your expectations of Nim in 2023 there.

  What have I done in the past week

  I work on all kinds of problems such as bugs, features, clean-ups and most importantly the roadmap.

  Clean-ups

  fixes comments about type bound operations

  remove legacy code; the first iteration now can build Nim with cpp backend

  closes #1072; add a test case

  use {.push warning[BareExcept]:off.} to override settings temporarily

  add deprecated warnings for {.deadcodeelim: on.} because the dead code elimination is always on.

  Bug fixing

  fixes #21360; discarding empty seqs/arrays now raises errors

  Features

  fixes #19291; implements `wasMoved` hook

  Roadmap

  fixes #19795; fixes #11852; remove parsing pipeline, Nim now parses the whole module at one time which now is listed on the roadmap and is the first step towards removing the need of forward declarations, which also fixes push pragmas within procs and fixes procs/iterators declarations disturbing the destructors analysis.

  Potential implications

  • Top level {.experimental: "codeReordering".} won't work anymore, you must pass it to the command line. This is beyond repair with the new parsing strategy.
  • {.overflowChecks: on.} and {.overflowChecks: off.}, which were misused to override settings temporarily, won't work like before anymore. The last overflowChecks setting will decide whether overflow checks will be enabled.

  What you could contribute to

  nimble develop -g doesn't work A possible solution is to add "g" to where "global" is placed.

  add changelog for nimble 0.14.0 breaking changes

  remove `codeReordering` in `db_connector/db_sqlite` Replace codeReordering with forward declarations.

---

• pietroppeter (orginal) [2023-02-20T11:00:50+01:00] view original

  Thanks for the write up and for the great work you have been doing! Btw, @ringabout did not mention it, but we have the golden opportunity of being part of their effort by sponsoring them! https://github.com/planety Let's not miss out! ;)

---

• ringabout (orginal) [2023-02-20T17:01:42+01:00] view original

  Thanks you!

---

• treeform (orginal) [2023-02-20T18:41:06+01:00] view original

  We need more of this! It it's hard to puzzle what is going on just based on commits. We might be able to figured out what happened, but not why it happened.

---

• ringabout (orginal) [2023-02-21T10:31:43+01:00] view original

  Sure thing! I'm going to do my best when I'm working on Nim.

  This week, I'm still following the roadmap and working on https://github.com/nim-lang/Nim/pull/21402 which intends to abolish (and deprecate) using passes in the compiler and simplify compilation pipeline, which should make the calling more clear.

---