Saem Ghani
Saem Ghani
First pass attempt at drafting a DOD AST based on this discussion: https://github.com/nim-works/nimskull/discussions/139 Breaks/Issues: - `ast.transitionX` procs now return a new node - no more nil means have to use...
## Summary * introduce test steps and assertions to testament's internal data model ## Details * --- ## Notes for Reviewers * very much a work in progress
## Summary * testament now tests with js and cpp targets more widely * consequently test target specification needed to be adjusted ## Details * this touches many test's specification...
Started as introducing knownIssue and disabled, but reworking internals heavily and minor consequences to the interface. Refactor Consequences: - introduces a more data oriented design - simplifies categories - remove...
Discovered by @zerbina attempting to run tests, they got an empty diff even though it was reported as a failure. This is for nimout related failures. ### Example Reproduction: -...
Testament presently treats `disabled` to mean two things: 1. this tests isn't working for some reason (issue, CI woes, etc) don't run it 2. disable it in certain parts of...
## Summary Large scale refactor: * compiler output data formats are owned by their respective modules * "reporting" is a consumer and no longer definer of formats * user diagnostics,...
Currently we have a `nimsuggest` which, when the compiler's semantic analysis works, provides autocomplete, documentation lookup, and more. This is via a protocol unique to `nimsuggest`. On the other hand...
Many people use VSCode or the like. At present most can make do with the [Saem's Nim](https://github.com/saem/vscode-nim) extension for Nimskull. Things are starting to diverge, however. Roughly what needs to...
## Summary * rework sem compiler proc `semProcAux` to use nkError ## Details * tbd --- ## Notes for Reviewers * still work in progress, doing an initial naive conversion...