feat: add a main crate to provide a clean user API #160
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.
This PR adds a new crate:
honeycomb
. It is only made up of re-exports from the core, kernels and render crates. The goal is to provide a single dependency for users in order to (a) simplify usage, (b) avoid dependency issues where the user disable features of a crate only for another crate to enable those back.All items of the respective core, kernels & render crate are accessible through re-exports; Additionally, a
prelude
module is defined with commonly used items.Ideally, this crate can be published with
1.0.0
; I just need to try and get thehoneycomb
package name from crates.io since the current project using it looks dead.Scope
Type of change