Quarter four 2025: chore backlog

[kaleidawave]

Here are a list of 'micro issues' unrelated to the checker or parsing bugs

CI: Publishing

• Use latest crates-release-gh-action with version_sync for crates
• Currently publish is two separate workflows: crates.io+npm publish and then GitHub release. Can this be merged into one?
  • Should try this on a smaller project before maybe 😅
• Use the script that concatenated GitHub commit messages?
• Use the now binary for adding date information into the binary
• Use the wrap binary for including contributor and sponsor information

CI: Checking

• Add back fuzzing
  • Waiting on Distributed release files can only compile for musl rust-fuzz/cargo-fuzz#355
  • and some more guidance on caching
• Want to add a step that checks for
  1. // TODO and // FUTURE comments
  2. dbg!, panic!(), unimplemented!(), etc
• Want to add ezno check parse + type check for the emitted ezno_lib.d.ts
• Want to add markdown formatting checks (using my simple-markdown-parser)
• Maybe GitHub workflow checks

CI: Information

• Use the new lines-of-code script (that contains function information etc). Should check the badges still work and possibly make a site
• Maybe replace bacon with script-runner?
• Is there a good place to report test262 findings?
• What is the state of automated fixes?
• Can performance checking be better?

Testing

• Want to add parsing tests based on spectra

CLI

• Finish REPL (and check it works with WASM)
• lahl -> see external

Parser - issues

• Use match_indices rather than finite automaton for identifier parsing
• Offset field does not do anything
  • Maybe offset should be a field on ParseOptions
• Change prefix code
• Further fixes to for loops, new lines etc
• Extract comments
• JSX and other extensions
  • JSX option should be Option<JSXOptions>
  • JSX statement mode?
  • Top level HTML mode

See #238

Parser - features

• Change to use reference &str for string literals, comments, declarations and identifier
  • This requires adding lifetimes to AST nodes, which we can automate with the tool I made a while back
  • Should double check the performance to see if worth it
• ... afterwards should allow for slab/pool allocation
  • With bumpalo crate
  • Again double check the performance to see if worth it
• Multiple parser errors Support emitting multiple parser errors #203

Checker

• Build and emit diagnostics on emit_diagnostic
• Use a vector in Environment (rather pointer chain)

External

• Update LAHL for WASM printing
  • Maybe more concise help message printing
• Update source-map
  • This has associated dependencies for self-rust-tokenise and codespan-reporting
• Spectra self test?