Closed 414owen closed 10 months ago
What's the rationale for this?
I have a project that I'm keeping quite lean, and at the moment async
is one of the two dependencies that depends on hashable
.
In general, minimizing dependency footprints gives us some small wins:
hashable
)Admittedly I might be scraping the bottom of the barrel trying to get rid of hashable
... Feel free to close this.
This seems to me a very narrow use case and not worth adding conditional compilation for. If there's a lot of demand then I'll reconsider. Closing for now.
This allows people to disable the Hashable instance, and dependency. To keep compatibility, it's implemented as a flag that defaults to true. I think that if async were to release a new major version, it would be good to implement this as a sublibrary instead.