> For example, the discussion about GDB support and the state of GDB front ends > was very interesting, but I did not understand the final conclusion about the > state of GDB support. Does the latest Nim support better variable printing? > Was the project abandoned? Araq gave up on lldb, but Arne did some GDB python > integration, what was the final result of that?
`tools/nim-gdb.py` and `bin/nim-gdb` is in devel. > I'm personally very interested in the state of destructors, but it is unclear > to me how finished that feature is. From what I know, the feature itself is > implemented, but in alpha state. How far along is new string and seq > implementation. When is that expected to arrive? Where is it being worked on > (some secret local branch on Araq's pc, lol)? It's in devel, unusable, but behind the `--gc:destructors` switch. Beta quality is expected to arrive end of January. > I have the same questions regarding the incremental compilation. > Bootstrapping with incremental is awesome, and the discussion was very > insightful, but what is the next step for this feature, and when / where is > incremental being worked on? Same story, behind an `--incremental:on` switch but not hidden in a branch. Next steps: * Writing tests for it. * Make the AST reloads lazy in order to improve performance. * Make the C codegen cache its results too, currently only the frontend processing is cached. Unknown release date. > This dev blog is probably not the best place for that info, but It highlights > something I wish Nim had: A clear high level roadmap and status about what is > currently being worked on. I don't think github issues is good enough for > this. It requires something more curated and more prominently advertised (on > the main nim website probably). Will think about this, in the past the roadmap we had was hardly maintained and github issues are but I'm sure we'll find something that works better.
