Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tree-0.4.1 beta regression #43682

Closed
est31 opened this issue Aug 5, 2017 · 2 comments
Closed

tree-0.4.1 beta regression #43682

est31 opened this issue Aug 5, 2017 · 2 comments
Labels
C-bug Category: This is a bug. regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@est31
Copy link
Member

est31 commented Aug 5, 2017

tree version 0.4.1 regressed from stable to beta (full log):

Aug 04 01:44:04.757 INFO kablam! error: use of unstable library feature 'ord_max_min' (see issue #25663)
Aug 04 01:44:04.757 INFO kablam!    --> src/set.rs:235:48
Aug 04 01:44:04.757 INFO kablam!     |
Aug 04 01:44:04.757 INFO kablam! 235 |     pub fn max(&self) -> Option<&T> { self.map.max().map(|e| e.0) }
Aug 04 01:44:04.757 INFO kablam!     |

cc @apasel422

@arielb1 arielb1 added regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. labels Aug 5, 2017
@arielb1
Copy link
Contributor

arielb1 commented Aug 5, 2017

@Mark-Simulacrum Mark-Simulacrum added the C-bug Category: This is a bug. label Aug 10, 2017
@alexcrichton
Copy link
Member

The libs team decided today that this is accepted breakage, so I'm going to close. cc @KodrAus though if you'd like to send a PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug. regression-from-stable-to-beta Performance or correctness regression from stable to beta. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

4 participants