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

Make "collections" feature optional #14

Merged
merged 1 commit into from
Nov 16, 2024
Merged

Conversation

simnalamburt
Copy link
Contributor

This PR allows bumpalo-herd users to freely enable and disable various feature flags of bumpalo.

@vorner
Copy link
Owner

vorner commented Nov 3, 2024

Er, why do we need this? Is it common that someone would depend on bumpalo-herd, but wouldn't be using bumpalo itself directly too? If it is not common, would it make sense to enable the features directly on bumpalo?

There's no actual code / support for these in the crate, these just… manipulate the dependencies this crate doesn't really need…

@simnalamburt
Copy link
Contributor Author

For the most part, you’re correct, but I wanted to provide an option to disable the “collections” feature. And also in #15, bumpalo-herd also depends on “allocator_api” and “allocator-api2,” so I exposed the feature flags in this way.

@simnalamburt
Copy link
Contributor Author

simnalamburt commented Nov 4, 2024

I have just closed PR #15, so perhaps you are correct that this patch is unnecessary, except for making the “collection” feature optional. I'll change the PR.

@simnalamburt simnalamburt changed the title Expose bumpalo features Make "collections" feature optional Nov 5, 2024
@vorner vorner merged commit d1efb2a into vorner:main Nov 16, 2024
1 check failed
@simnalamburt simnalamburt deleted the patch-1 branch November 17, 2024 09:59
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