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

Brilirs stable #125

Merged
merged 1 commit into from
Jun 18, 2021
Merged

Brilirs stable #125

merged 1 commit into from
Jun 18, 2021

Conversation

Pat-Lafon
Copy link
Contributor

With Rust 1.51, #![feature(or_patterns)] should be stablized. This pr moves brilirs back on to the stable channel. This pr is dependent of #122.

See https://forge.rust-lang.org/ for the rust release schedule. The current date is March 25th.

@sampsyo
Copy link
Owner

sampsyo commented Feb 5, 2021

Cool! To clarify, should we hold off on merging this until 1.51 is out?

@Pat-Lafon
Copy link
Contributor Author

Yes, with the release of 1.51, this pr can be committed(baring any future merge conflicts). brilirs will not compile with this change on stable 1.49(1.50 in a couple days).

@Pat-Lafon
Copy link
Contributor Author

I have been bamboozled, 4 days ago, the version for stabilizing the or_patterns feature was changed to 1.53 which becomes the stable version on June 17th. rust-lang/rust#79278

@sampsyo
Copy link
Owner

sampsyo commented Mar 24, 2021

Ah! That ol' stabilization treadmill. 😃

@Pat-Lafon
Copy link
Contributor Author

4 months later, this commit now works as expected on the latest stable release and is ready to be merged.

@sampsyo
Copy link
Owner

sampsyo commented Jun 18, 2021

Yay!! Thanks, @Pat-Lafon!!

@sampsyo sampsyo merged commit 84891e8 into sampsyo:master Jun 18, 2021
@Pat-Lafon Pat-Lafon deleted the brilirs-stable branch July 19, 2021 04:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants