Lithe-POC VS starlight

For the month of March, my actual goal is to consolidate all my skills. Just like for the past several years, I want to break into making money through reinforcement learning in particular. I want to get good at nurturing my agents and using them. I've set a rule for myself that the games I will be training them on should be interactive. It is just such obvious loser behavior to be doing everything from the command line. That having said, until I learned how to do reactive programming properly just recently meeting that goal seemed impossible. Programming is the kind of activity where you can sit down and grind away at it and make progress, so the weak and stupid can do it too, but to achieve true excellence rather than a mess, you need the right tools and techniques.

I have great news

Hello to all! This crate implements Shadow Stack algorithm which allows to track GC objects on stack with almost zero overhead! This algorithm is used inside Restricted Python and seems to work very well. This crate soon will replace DIY shadow stack implementation in starlight(JS engine in Rust) too.

Working on startup snapshots in starlight. I already have very basic implementation which allows to initialize runtime in just 17 microseconds from snapshot vs 23 microseconds without snapshot when every builtin is created from scratch. Future work is aimed mostly on making deserialization faster

Hi to all! I'm working on starlight (JS engine in Rust) and I can't choose memory management technique: Right now I have conservative on stack precise on heap GC which somehow manages to work but still has segfaults and I'm also working on rcgc feature which will use RC as GC algorithm but my main question: is it worth using RC over tracing cycle and how hard it will be to implement JIT when RC is used? I've never seen any runtimes that use RC and implement JIT.

There's test262_passed file in repo, you can take a look at what tests pass :)