{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreia2rwh4chxpuefcfis3aasacpbyczb337xz5mg3rabdazwn77tuia",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mfhpgdl47d22"
  },
  "path": "/t/custom-cargo-command-to-show-only-errors-avoid-setting-rustflags-every-time/24032#post_4",
  "publishedAt": "2026-02-22T17:45:35.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Noratrieb:\n\n> I think it would be nice if we had a way to make the errors more visible than the warnings. Maybe something like re-printing errors at the end of the build log if there were several warnings?\n\nErrors themselves can be just as problematic as warnings — e.g. some erroneous code can break trait solving for the rest of the program, resulting in a flood of errors around `Sized` or other ubiquitously used traits. I would say the most valuable UX change would be to reprint or otherwise draw attention to the **very first error** , which is the one most likely to be accurate and relevant.",
  "title": "Custom Cargo Command to Show Only Errors (Avoid Setting RustFLAGS Every Time)"
}