Absolutely not! We're dog-slow compared to V8, and about 2x as slow as Boa as well.

The project is first and foremost an exploration of data-oriented design in JavaScript engine development. I do hope that will eventually make us really fast on the happy path, but it's nowhere near that today.

Sing it, with pathos!

Having just taken a nap, I can concur. I wish to repeat the experience.

This combined with another post about "a girl of unknown provenance" makes me think that interpretative dance would be a good medium for exploring pointer provenance in #Rustlang and C/C++.

Oops, I was under the impression that integer overflows were UB in release mode, but that's wrong. So you're absolutely right, memory safety isn't compromised by integer overflows.

If you do have any unsafe code then it does make memory safety bugs much easier to introduce by accident, though.

Yeah, but (arguably) overflow checks are just another factor of memory safety.

Kauppuri 5 is definitely a must visit on nearly every Oulu trip!

If your company is interested in funding Rust maintainers, please reach out to me or @erikjee.bsky.social!

You can find our sponsors prospectus here: rustnl.org/resources/Ru...

Let me know if you want to talk! 💛

(Message me through Bluesky, Mastodon, Rust Zulip, or email: [email protected])

Did you know you should support Z? I think it makes sense for you to support Z, as your CTO founded Z. Here's why I think supporting Z would be a game changer: I use Z, and all the people in the Z community would nod along vigorously if you supported it. They probably wouldn't use it though.

is not sadness that piles up. It is joy, happiness, contentedness. If there is some sadness piling up, it is sucked into the vacuum cleaner every week, leaving only a surface clean of sadness but layered in joy.

I hope I'll remember this feeling in the future when I have a need to.

そうですが、ウーバーフローも安全に関するもので、正直あれを消さない方がいいです。releaseビルドにoverflow-checks=true追加することを勧めします。

I just applied and got my vacation days for the trip! But I'm not a Bevy user or developer at all :(

Torille!

It's probably not an active problem per se, but it's the kind of thing that keeps language designers awake at night: if you make clones willy-nilly you'll be known for autoclone as a footgun, if you make clones explicit you'll be known for being verbose. If you make it configurable, you're annoying.

It seems to arise directly from applying substructural logic on type systems. I'm no type systems person though, so I cannot answer any more thoroughly than that :)