-
Notifications
You must be signed in to change notification settings - Fork 41
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
Create a new crate for procedural macro #32
Comments
la10736
changed the title
Create a new create for procedural macro
Crate a new create for procedural macro
Apr 30, 2019
Closed
la10736
changed the title
Crate a new create for procedural macro
Create a new crate for procedural macro
Jun 28, 2019
Ok, I did a test and the idea works. But I don't need it for 0.3 release because I'll can use reexport to don't bother users on change
|
la10736
pushed a commit
that referenced
this issue
Apr 5, 2022
la10736
added a commit
that referenced
this issue
Apr 24, 2022
Done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Investigate if
rstest
can be a non procedural-macro's crate that reexport the macros. So move macros in a new crate, reexport them and use rstest just for container crate (core logic if need) and reexport some base fixtures.The text was updated successfully, but these errors were encountered: