zc he
`nushell/nu_scripts` is now tracked by the [CI workflow](https://github.com/nushell/tree-sitter-nu/blob/main/.github/workflows/ci.yml#L40) .
Related tree-sitter issues: https://github.com/tree-sitter/tree-sitter/issues/4091, https://github.com/tree-sitter/tree-sitter/issues/3966 For some reason, the bug tag was removed 4 days ago. Maybe the authors thought it was a grammar issue. Generally I have no idea...
> It may be worth tracking building with WASM. Last run for me was `6min 49sec`. I got these error messages, do you know where's the problem? ``` ▓ ...
> My guess is because of the warning amd64 vs arm64 Oh, they look so similar, and I didn't notice the diff, lol.
> After #189, `tree-sitter build -w` is `2min 7sec`. wow! Seems that the case statement count is indeed the very target to optimize.
After #205 : ```nushell tree-sitter generate --report-states-for-rule - e>| "name\tcount\n" ++ $in | detect columns | take 10 | to md ``` |name|count| |-|-| |val_range|817| |expr_binary_parenthesized|614| |_repeat_newline|490| |_immediate_decimal|430| |_val_range|387| |_val_number_decimal|315|...
## Latest numbers: ```sh > rg "#define.*STATE" src/parser.c ``` > 16:#define STATE_COUNT 5237 > 17:#define LARGE_STATE_COUNT 1273 ### Case count of `ts_lex` 2192 ### Top Results of States for Rule...
> We discussed this in the meeting yesterday, and we generally agree this is a good way forward. We would also really like to see spans being passed to internal...
https://github.com/nushell/reedline/pull/428 BTW, I can't reproduce the bug in the recording with these changes reverted.
BTW, some duplicated code here with no harm: https://github.com/nushell/nushell/blob/e0bc85d0ddb4d6641cffa8567e549b105638c506/crates/nu-lsp/src/notification.rs#L67-L81