Regression report stable-2016-10-20 vs. nightly-2016-10-21

Regression report stable-2016-10-20 vs. nightly-2016-10-21

  • From: stable-2016-10-20
  • To: nightly-2016-10-21

Coverage

  • 5693 crates tested: 3473 working / 1266 broken / 75 regressed / 235 fixed / 644 unknown.

Regressions

  • There are 56 root regressions
  • There are 75 regressions

Root regressions, sorted by rank:

Full report.

The unused_qualification warnings from try!() seem like something that is really a bug on rustc’s end → issue 37345

Most of these regressions were caused by #37213 and will be fixed once #37361 lands.

These are the remaining regressions:

  • lint drop_with_repr_extern has been removed
  • lru_time_cache-0.5.0
  • kademlia_routing_table-0.6.0
  • get_if_addrs-0.4.0
  • libsodium_seeded_prng-0.1.1
  • message_filter-0.6.0
  • multiaddr-0.1.0
  • sodiumoxide_extras-0.1.0
  • vsop87-1.0.4
  • #[deny(transmute_from_fn_item_types)] on by default
  • td_rlua-0.1.3
  • hlua_master-0.1.8
  • zmq-rs-0.1.7
  • use of deprecated item std::hash::SipHasher
  • message_filter-0.6.0
  • multiple applicable items in scope (issue #37354)
  • mbox-0.1.3
  • the trait bound `Self: std::marker::Sized` is not satisfied
  • cfg-regex-0.0.0
  • lense-0.1.2
  • vectormath-0.1.1
  • the trait bound `[u8; 1024]: std::cmp::Eq` is not satisfied
  • assimp-0.1.0
  • pascal_string-0.4.0
  • can't find crate for `nuklear_sys`
  • nuklear-backend-gfx-0.1.3

These two are due to #36830. I have published the fix for assimp.

nuklear-sys is https://github.com/rust-lang/cargo/issues/3214

Is there an issue for “the trait bound Self: std::marker::Sized is not satisfied”?

Is there an issue for "the trait bound Self: std::marker::Sized is not satisfied"?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.