Inline predule
module contents into their parent modules
#972
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.
We've never used
prelude
in a sensible way, both modules inside the crate root andvk
namespace have always abused these modules to store a random combination of private utilities next to a few extra hand-written type/trait definitions and implementations, as outlined before in #879 (comment).Neither of these need to glob-imported by users to make easy use of
ash
functionality besides perhaps ensuring traits likeHandle
andTaggedStructure
are in scope. Their glob imports were only useful toash
itself, and even then thevk::prelude
was already fully glob-reexported invk
.Besides inlining its contents, I've shuffled some private helpers like
debug_flags()
closer to where they are being used.