rapydscript-ng 0.8.2 → 0.8.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +11 -0
- package/local-agent.md +4 -0
- package/package.json +1 -1
- package/release/compiler.js +5125 -5115
- package/release/signatures.json +6 -6
- package/src/ast.pyj +18 -25
- package/src/output/functions.pyj +111 -13
- package/src/output/loops.pyj +31 -9
- package/src/tokenizer.pyj +17 -5
- package/test/str.pyj +10 -0
- package/tools/cli.mjs +4 -3
- package/tools/compile.mjs +9 -3
- package/tools/lint-worker.mjs +101 -0
- package/tools/lint.mjs +127 -8
- package/tree-sitter/grammar.js +27 -6
- package/tree-sitter/queries/highlights.scm +10 -0
- package/tree-sitter/src/grammar.json +130 -5
- package/tree-sitter/src/node-types.json +73 -0
- package/tree-sitter/src/parser.c +119589 -114993
- package/tree-sitter/src/scanner.c +275 -17
- package/tree-sitter/test/corpus/strings.txt +41 -5
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,14 @@
|
|
|
1
|
+
version 0.8.3
|
|
2
|
+
=======================
|
|
3
|
+
|
|
4
|
+
* ``lint`` command now uses a worker thread pool for large jobs, roughly
|
|
5
|
+
doubling throughput when linting many files at once
|
|
6
|
+
* Fix string concatenation across newlines inside function calls not working
|
|
7
|
+
when one of the strings is an f-string
|
|
8
|
+
* Tree-sitter grammar: f-string expressions inside ``{...}`` are now
|
|
9
|
+
structured as ``interpolation`` nodes, enabling syntax highlighting of
|
|
10
|
+
the embedded expressions in editors that use the tree-sitter grammar
|
|
11
|
+
|
|
1
12
|
version 0.8.2
|
|
2
13
|
=======================
|
|
3
14
|
|
package/local-agent.md
CHANGED
|
@@ -26,3 +26,7 @@ run the entire suite.
|
|
|
26
26
|
Before declaring a task complete, you must follow this exact verification lifecycle:
|
|
27
27
|
1. Run the local **Build and Test Command** to guarantee zero compilation or compilation-stage errors and no test failures
|
|
28
28
|
2. If errors occur, analyze the stdout logs completely before writing a fix. Do not guess.
|
|
29
|
+
3. Run ``rapydscript fmt src`` to ensure any changes you made to .pyj files are
|
|
30
|
+
correctly formatted
|
|
31
|
+
4. Run ``rapydscript lint src`` to check for any issues in your code
|
|
32
|
+
5. If the changes you made are user visible, update the changelog
|