Simplify feature dependencies
- We only use
futures-util'sallocfeature in the tests. futures-coreonly has one feature and that is alloc and it is on by default.
While this is a nice simplification, I am not sure if it is necessarily a good idea. It is a little less clear exactly what features are enabled and which aren't, as we are relying on what the default features are, as opposed to writing them out ourself. What do you think?
While this is a nice simplification, I am not sure if it is necessarily a good idea. It is a little less clear exactly what features are enabled and which aren't, as we are relying on what the default features are, as opposed to writing them out ourself. What do you think?
I would expect futures-core to always be extremely lightweight so the risk of having more code "slip in" is quite low I believe. Plus, I'd expect any changes to features to result in a minor version bump as they can be breaking.
Happy to change it back but I also like the simplicity of not needing to set features. I do see though how it can trigger the thought of "did we vet the default features of this lib?".
I wish default features would have never been introduced :(
I would expect futures-core to always be extremely lightweight so the risk of having more code "slip in" is quite low I believe. Plus, I'd expect any changes to features to result in a minor version bump as they can be breaking.
Fair enough.
Happy to change it back but I also like the simplicity of not needing to set features. I do see though how it can trigger the thought of "did we vet the default features of this lib?".
Yea, this was my main point
Happy to change it back but I also like the simplicity of not needing to set features. I do see though how it can trigger the thought of "did we vet the default features of this lib?".
Yea, this was my main point
Do you want me to add a comment?
I think that's a good solution, thanks :)
Thanks for adding the comment! Can be merged after conflicts are resolved
Resolved! Sorry for the delay.