Make a "trampoline" crate to avoid unneeded dependencies in a proc-macro crate #5
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.
wasm-bindgen
causes some issues when building as a part of a proc-macro (see rustwasm/wasm-bindgen#3457). But we still want to enforce the correct version bounds on it, so that the generated code did not turn out to be incorrect/un-compileable. This PR creates a proc-macrowasm-bindgen-derive-macro
crate and simply re-exportsTryFromJsValue
inwasm-bindgen-derive
.wasm-bindgen-derive-macro
only contains proc-macro dependencies (syn
and so on), andwasm-bindgen-derive
contains the dependencies for the generated code (wasm-bindgen
andjs-sys
)Fixes #3