[Snuggly73]

error: could not compile `fastrender` (lib) due to 34 previous errors; 94 warnings emitted

I guess probably at some point, something compiled, but cba to try to find that commit. I guess they should've left it in a better state before doing that blog post.

[jaggederest]

I find it very interesting the degree to which coding agents completely ignore warnings. When I program I generally target warning-free code, and even with significant effort in prompting, I haven't found a model that treats warnings as errors, and they almost all love the "ignore this warning" pragmas or comments over actually fixing them.

[ianbutler]

Yeah I've had problems with this recently. "Oh those are just warnings." Yes but leaving them will make this codebase shit in short time.

I do use AI heavily so I resorted to actually turning on warnings as errors in the rust codebases I work in.

[conception]

You can use hooks to keep them from being able to do this btw

[suriya-ganesh]

unfortunately this is not the most common practice. I've worked on rust codebases with 10K+ warning. and rust was supposed to help you.

It is also close to impossible run any node ecosystem without getting a wall of warnings.

You are an extreme outlier for putting in the work to fix all warnings