On: Rust Dylib Rabbit Holes

[ninkendo]

Interesting, now I feel like an idiot. I had assumed cargo check performs a superset of cargo build (as in, lint checks/etc) but looking at the docs you’re right, it does seem to be aimed at doing exactly what I describe, skipping final compilation steps and just checking if the code has errors.

Time to re-bind my IDE shortcuts!

[ninkendo → ninkendo]

Oh but also, from the docs:

> Some diagnostics and errors are only emitted during code generation, so they inherently won’t be reported with cargo check.

I’ll have to see how much this affects my work loop but it’s definitely worth trying.

[gpm → ninkendo]

Huh, I have been programming in rust for a long time and I've never noticed such diagnostics.

Well, unless you count an unintentional LLVM crash as a "diagnostic or error", then I've noticed one exactly once...

[skitter → gpm]

I believe post-monomorphization errors don't show in cargo check, and those are rather rare in Rust.

[lor_louis → skitter]

Cargo check won't report linker errors, that the only difference I ever ran into.

[ninkendo → ninkendo]

Update: after 2 days of replacing my “cargo build” shortcut with “cargo check”, I never saw an error that check didn’t catch.

Granted, most of my build/edit loop consists of attempting to build not-working-yet code anyway, so build was typically halted due to errors before linking happened in the first place, so in practice I don’t think it’s saved me that much time… but in the few cases where everything does build, it’s nice to not have to wait those extra few seconds for the green check (I’m using RustRover for the record.)