😭 Because I think this combination makes development the most efficiency.

I love JavaScript but I also want Rust Syntax. I love Rust but I also want GC.

(Inspired by www.joshuakgoldberg.com/blog/rust-ba...)

btw, object property mangling is not directly related to tree-shaking 😇 Let's think of a new name to replace the temporary one "Tree Shaker" plz 🥹

Despite this problem, it's making progress! It was made 3.4x faster 4 days ago🥰
codspeed.io/KermanX/tree...

Another option is to use a new "consumed dependencies" scope for each pure call, but this will make consumable impossible to use a flag to avoid being referred twice (for performance). Because entities can be consumed in a pure call, and later in a non-pure.

I once tried making the return value a "computed" with every consumed thing in the function execution as its dependency, but this is quite tricky and buggy because every consumed dependency have to be attached to something in the pure call.

In tree shaking it should be something like "If and only if the return value is retained, retain the function call". However, there is no way to know whether the return value is used or not before completing the analysis of the whole program.