Did you check sonic_rs ? I've been using that and it seems to work great.

Have nice fantasy series recommendations?

Although you know, I wonder if someone could craft a minified payload that, as the LLM tries to decipher it (and they are surprisingly good at that), could lead to prompt injection.

One of the tricky part I faced was that to make this work, you need to turn the function into a state machine. With loops, initializers, etc it's not exactly trivial.

The Next.js workflow stuff is very similar; the difference is that instead of creating the new iterator right away they serialize it. Future forks only need to be restored from that snapshot.

For context, I wanted a way to "fork" generators so new iterators could be created at any yield point. Those new iterators had their own stack and could progress without impacting the original iterator (assuming they only had access to immutable data structures).

Should have done it in Rust / C# / C / ASM / [...]

⏸️ Neutral exit codes and early bailouts
♻️ Require branches to be up-to-date as of <commit> to merge

Fascists are known for their severe nut allergies

That's why you're supposed to have good observability, to alert you when numbers go way off!

I check from time to time and what remains of tech there is mostly either people that need to sell something or folks who feel fine expressing thoughts I don't align with. It's essentially LinkedIn if it had the same tech bro mentality as the early 2000s.

It also doesn't seem to be using the errors shown in the IDE to autocomplete the fix; is it because I'm using the free version?

The @zed.dev auto-completion doesn't seem to leverage my previous edits as well as Cursor though - it keeps suggesting edits in a shape I already had to partially rewrite for previous occurrences of the same code pattern

Did it all start with @nicr.dev being nerd snipped? 😛

Did you try to run Next.js with those APIs?