Instead of "possible" undefined behaviors, potential bugs, the samples I've randomly picked are all actual undefined behaviors, real bugs. Hence statistically.
> pointer aliasing is undefined behavior in both languages
That included and also basically every other claim in that comment. I'd be happy to learn otherwise if you have concrete evidence.
[Edit: erased information that can help people find the bugs without prior knowledge]
> I haven't said that you have to provide evidence of them
Sure, but if I'm going to it would be a lot easier to convince everyone how bad it is (just like I did in private message groups). I can't take the risk that "everyone" also includes Jarred though.
> you can grep for these bugs now
You can grep for the greppable new bugs. I raised them as an argument because these issues are glaring. What about the ungreppable ones? More than half (again, randomly sampled) unsafe usage in the 10,413 unsafe blocks in current Bun looks iffy to me. I just haven't taken the time to verify them because many requires reasoning across the code base (see? the exact problem Rust ought to prevent). From a Rust point of view it's a huge failure.
All these while considering that the Bun agents (no people at this point I'm afraid) don't even know how to grep for the easy ones.
This is going in circles. I think my point has been made. You can grep for every memory safety violation in Rust, that is a win. Pointer aliasing is apparently not UB in Zig, that's cool, assuming that's what you are referring to - but I just can't stress enough how little this matters to my point.
> pointer aliasing is undefined behavior in both languages
That included and also basically every other claim in that comment. I'd be happy to learn otherwise if you have concrete evidence.
[Edit: erased information that can help people find the bugs without prior knowledge]
> I haven't said that you have to provide evidence of them
Sure, but if I'm going to it would be a lot easier to convince everyone how bad it is (just like I did in private message groups). I can't take the risk that "everyone" also includes Jarred though.
> you can grep for these bugs now
You can grep for the greppable new bugs. I raised them as an argument because these issues are glaring. What about the ungreppable ones? More than half (again, randomly sampled) unsafe usage in the 10,413 unsafe blocks in current Bun looks iffy to me. I just haven't taken the time to verify them because many requires reasoning across the code base (see? the exact problem Rust ought to prevent). From a Rust point of view it's a huge failure.
All these while considering that the Bun agents (no people at this point I'm afraid) don't even know how to grep for the easy ones.