This repository was archived by the owner on Dec 11, 2024. It is now read-only.
Closed
Conversation
Author
|
Nevermind - looking more closely it does look like you lose the parallel iterator without this flag. It might be cool to do something like this to make rayon an option for h3ron clients. But I'll try that another time perhaps. |
Owner
|
Thanks for bringing this up - I had not noticed this. The activated hashbrown features where generally in conflict with the h3ron featuregates. 65abf80 should fix this. |
Author
Thanks for fixing this up! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When trying to use h3ron v0.12.0 without any features, rayon still gets pulled in. This is because hasbrown now depends on it as a feature, but it appears it might be unnecessary?