New week, new Rust! What are you folks up to?
Working on supply chain security. I've implemented checking whether published crates match their git repositories, and I'll add some UI for reviewing the differences.
I'm hacking on a language server and VS Code extension for the *.wit
files used in the WebAssembly Component Model.
So far I've put together a parser (using Tree Sitter), syntax highlighting, basic diagnostics, code folding, completion, and selection ranges. Next up is to finish lowering from a Concrete Syntax Tree to some sort of HIR so I can do more elaborate semantic operations like Go To Definition and automatic refactors.
I tidied up my BTreeMap, I think it is now nearly finished...at last... (!).
If anyone wants to try it out ( you should just be able to use it as a replacement for BTreeMap, and it should use less memory and be a bit faster, plus the new Cursor API is available not just on nightly ), please do, and let me know of any problems.
I also tried out CursorMutKey in my database software ( it maintains a map of writes ). That is here: wmap.rs - source
Working hard to learn how to add a menu to an fltk.rs TextEditor. You'll see a post in the help category pretty soon.
I'm working on a terminal based game, just for fun. It consists of a "gamification" of a certain span memory test. It is not complete yet, but it's playable.
My project is a new Hardware Design Language called "SUS" that focusses on making hardware design far far terser, while still allowing full control over the generated hardware: GitHub - pc2/sus-compiler: A new safety-first hardware design language
It's got both the Compiler and Language server as part of the same project, and they share most of the pipeline.
The parser's built using Tree-Sitter. On forums people argued against using it as a compiler frontend but I'm liking it a lot.
Having suffered with asking "WTF where is this commit hash in .cargo_vcs_info.json
" in crates that shall not be named, thank you!
This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.