Second time[1] attempting to post this plagiarised repo, now with a different name. Clearly forked from rustd, with the user prompting Claude to rename it and scrub references to it. The LLM helpfully notes "rename rustd (rustd stays credited)" and yet there are no mentions of it in licensing. Last time you submitted it on your personal account, now I guess you're submitting it on a bought account?
> The borrow checker is new: 0.1.0 has none, so an edit with a borrow error builds and runs; the one on main finds about two thirds of rustc's borrow errors.
Unfortunate naming which conflicts with Google’s Blaze, but I would love to integrate this with Bazel persistent workers. Bazel, for the most part, can build Rust better than cargo can.
It’s unfortunate that Rust’s incremental compilation has so many bugs with -Z threads, maybe this can work around that.
Second time[1] attempting to post this plagiarised repo, now with a different name. Clearly forked from rustd, with the user prompting Claude to rename it and scrub references to it. The LLM helpfully notes "rename rustd (rustd stays credited)" and yet there are no mentions of it in licensing. Last time you submitted it on your personal account, now I guess you're submitting it on a bought account?
[1] https://news.ycombinator.com/item?id=50168220
Median 19x faster
Min 3.7x faster
Max 83x faster
(Calculated from 25 benchmarks: https://github.com/indexable-inc/blaze/blob/main/docs/benchm...)
I'm sure there are builds that are faster than 92x. Is this a flaw in common vernacular?
Not really, since I’m pretty sure we all know what they meant. They meant it was up to 92x faster in their testing.
> The borrow checker is new: 0.1.0 has none, so an edit with a borrow error builds and runs; the one on main finds about two thirds of rustc's borrow errors.
https://github.com/indexable-inc/blaze/blob/main/docs/usage....
Hey what could go wrong? You didn't really need 33% of your borrow-checking anyways.
Only one contributor with more than four commits.
Initial commit was 7 days ago. I guess now we have a "vibechecker"!
Unfortunate naming which conflicts with Google’s Blaze, but I would love to integrate this with Bazel persistent workers. Bazel, for the most part, can build Rust better than cargo can.
It’s unfortunate that Rust’s incremental compilation has so many bugs with -Z threads, maybe this can work around that.
> Unfortunate naming which conflicts with Google’s Blaze
This isn't even a public tool so how exactly does it conflict?