-
Notifications
You must be signed in to change notification settings - Fork 506
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
Rayon 0.7.1 is broken #364
Comments
To be clear, stable We don't have a really good story for how we change unstable features. We could make If you can't upgrade, then you could also manually pin We should probably think about stabilizing those features, and avoid adding new features this way, because it won't fly well long term... |
Oh, that makes sense. The issue was actually not in my library, but in the |
Yes, Servo was also encountering a similar problem. This just serves to reinforce the reason that the Rust project has always drawn a big, bright line around unstable features. I guess we have to do the same. |
Closing this issue, as I don't think this is a bug itself. But I opened https://github.com/nikomatsakis/rayon/issues/369, which is a proposal for a new way to handle unstable APIs. |
Rayon 0.7.1 compilation fails with the following error:
I assume that this is a dependency specification issue, as rayon-core was recently updated to change the name of
spawn_async
.The text was updated successfully, but these errors were encountered: