Post

Great article, thank you! I had seen the recommendation of putting the AST in a flat array, but hadn't thought of the JS class idea. That makes the idea a lot more applicable for my linter! I have a few questions if you don't mind (feel free to reply at the end so we don't have many threads)

In practice this doesn't talk much about Rust, this is mostly about passing the data from a Rust program to a JS program? There is no Rust involved in the evaluation of these rules, correct? So you have two systems for running rules: one for Rust rules and one JS plugin rules.

You mention it takes 20.4ms for the traversal (and selector matching). Is that faster/slower than with the original tree structure? The properties array contains very different data, which I'm therefore assuming isn't/can't be monomorphized. Is that correct?

Nice! This looks _very_ similar to how the React DevTools serializes updates to the component tree: blog.isquaredsoftware.com/presentation... /cc @brian.blue

yeah there are a few similarities in the way the encoding is done. I'd say the key difference is that React DevTools thinks more in terms of operations rather than a full tree structure. All Fibers have the same structure too. Props are different but they're only loaded when you click a node.

I miss bookmarking feature here on bluesky a lot now. I got all previous posts on this bookmarked on twitter 😭