-
Notifications
You must be signed in to change notification settings - Fork 953
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
Re-export public dependencies #5063
Re-export public dependencies #5063
Conversation
b76e6c1
to
a3dfbe3
Compare
a3dfbe3
to
f47675e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cfgs all look right to me, just a few cosmetic comments
this will be super useful!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cfg
s seem fine to me.
I think renaming the documented cfg
with doc(cfg(...))
like you did is a good idea.
I wonder if it's worth documenting the feature shorthands in the lib.rs file so the user knows what to expect and we don't need to rename all the shorthands |
I believe this would be an improvement in any case 👍. |
f47675e
to
3baede1
Compare
3baede1
to
6032442
Compare
Closes #5054.
Useful enough to have, and doesn't clutter things too much.
This re-organizes our naga dependency a bit, notably that it's now properly optional on wasm, only enabled if you enable a feature that requires transpilation, or a direct mention in our public interface.