You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As rust projects grow it becomes more important to have excellent error messages.
Part of that is being able to pinpoint the source span of an issue in a particular Cargo.toml (in the same way that rustc does). This enables IDEs to be able to go directly to the source line in question.
When we're dealing with one crate at a time this is less of an issue, but if you're dealing with 100 crates then line numbers really help speed up getting to the location of the error so that it can be quickly fixed.
(Apoligies if this is a dupe, I did look but surprisingly couldn't find a similar issue)
The text was updated successfully, but these errors were encountered:
I see we can use toml::Spanned for fields in the TomlManifest that we're interested in giving detailed line number information about - I'd suggest we start with just dev/build/dependencies having associated line numbers and see where we go from there.
As rust projects grow it becomes more important to have excellent error messages.
Part of that is being able to pinpoint the source span of an issue in a particular Cargo.toml (in the same way that rustc does). This enables IDEs to be able to go directly to the source line in question.
When we're dealing with one crate at a time this is less of an issue, but if you're dealing with 100 crates then line numbers really help speed up getting to the location of the error so that it can be quickly fixed.
(Apoligies if this is a dupe, I did look but surprisingly couldn't find a similar issue)
The text was updated successfully, but these errors were encountered: