Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Errors triggered by RFC 1214

Running target/debug/crater-cli report comparison 4b79add08653d89f08e5a5c94c2132515a1aa30f 358f1098db240f0d7ac40151388aea610242097c

Regression report 4b79add08653d89f08e5a5c94c2132515a1aa30f vs. 358f1098db240f0d7ac40151388aea610242097c

  • From: 4b79add08653d89f08e5a5c94c2132515a1aa30f
  • To: 358f1098db240f0d7ac40151388aea610242097c

Coverage

  • 2710 crates tested: 1525 working / 1161 broken / 9 regressed / 0 fixed / 15 unknown.

Regressions

  • There are 4 root regressions
  • There are 9 regressions

Root regressions, sorted by rank:

  • nickel-0.6.0 (before) (after)
    • Due to: incorrect lifetime annotations that somehow were not detected before. --nmatsakis
  • tendril-0.1.3 (before) (after)
    • Due to: incorrect lifetime annotations that somehow were not detected before. --nmatsakis
  • netlib-blas-provider-0.0.8 (before) (after)
    • Due to: appears to be a crater failure, rather than a genuine error. Attempts to build locally failed due to cmake errors configuring the fortran compiler. --nmatsakis
  • almost_ord-0.1.0 (before) (after)
    • Due to: use of <T as Iterator>::Item type where T: Iterator not specified. This is caused by the new, more thorough checking, and hence ideally would receive a warning, but because the error is triggered in a common subroutine, it is challenging to isolate it. --nmatsakis

Non-root regressions, sorted by rank:

Broken, sorted by rank:

Fixed, sorted by rank:

Working, sorted by rank:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.