Roadmap progress thread #142
Replies: 15 comments 1 reply
-
Finished and approved code of conduct
|
Beta Was this translation helpful? Give feedback.
-
Updated contribution, moderation and coding guidelines
|
Beta Was this translation helpful? Give feedback.
-
[@haxscramper] Implemented structured report system
|
Beta Was this translation helpful? Give feedback.
-
[help wanted] Working on - language specificationImplemented basic sections of the language specification, added toplevel documentation and reasoning for the language specification.
Language specification implementation progress can be split into many smaller contributions, and it will be a long-standing effort to create a comprehensive test suite that can actually ensure the language correctness. |
Beta Was this translation helpful? Give feedback.
-
[@alaviss] Working on - builder library for koch
|
Beta Was this translation helpful? Give feedback.
-
[@saem] Working on - testament rework
|
Beta Was this translation helpful? Give feedback.
-
[@shayanhabibi] Implemented
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
[@haxscramper] implemented - minor testament UX improvements |
Beta Was this translation helpful? Give feedback.
-
[@haxscramper] working on streamlining testament-compiler interactions and command-line processing |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
[@haxscramper] working on parser refactoring
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
[@zerbina] working on - refactoring of the compiler backend
|
Beta Was this translation helpful? Give feedback.
-
Closing in favor of https://github.com/nim-works/nimskull/milestones -- it is more automated, can be easily edited. Does not provide so detailed overview of the task dependencies, but I'm not exactly sure if this even necessary. |
Beta Was this translation helpful? Give feedback.
-
Thread is created in order to make it easier to keep track of what is being worked on, and what has already been implemented. This is a high-level overview of the current state of the progress - most of the relevant discussions and elaborations should still go in the respective PRs.
Roadmap log should only include things that are actually being worked on - this is not a todo list, but rather an ongoing log that (ideally) should help people realize where exactly we are now in the roadmap progress.
Current state of the near-term plans is show on the graph. It shows the actual state of the development at the moment, and due to the complexity of the overall refactoring might seem overly convoluted - that is not intentional, but is a direct consequence of the difficulty of the overall task.
Related discussions that go into more details of the particular steps
{.debug.} define
and compiler debugging Compiler debugging #197NOTE: the graph is created in SVG format, so you can open it in a separate tab and zoom in/out if you need to read a full description of the element.
The roadmap in the readme represents a long-term strategy that we will follow to the best of our ability, but along the way more problems are discovered that might temporarily change the importance of different tasks, or add new minor dependencies. These changes will be reflected on this graph instead. Graph source
Beta Was this translation helpful? Give feedback.
All reactions