-
Notifications
You must be signed in to change notification settings - Fork 45
Export macro test_vfs #18
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
Comments
Good point, thanks for the suggestion. It should be possible to export this with a feature gate. I will take a look at this tomorrow. |
Should work now in 0.5.1, please let me know if there are any issues. Cheers! |
Thanks, but there is still an issue: The macro tries to import VfsPath and VfsFileType from the current crate. Obviously, these are only available in VFS and not in other crates. I don't have an idea, how to solve this. Maybe the caller has to import these types? |
Could you try with ad1c22e, I changed the use declaration to use $crate, which might fix the issue. https://doc.rust-lang.org/reference/macros-by-example.html#hygiene |
Great! Now it works! |
Good to hear! Do you want me to publish another patch version so you don't have to depend on a git commit id? |
Yes, that would be great. |
If the vfs is extended by in another crate as suggested here, than the macro test_vfs! can't be used from the other crate, since it is only available for the tests. It would be nice, if this macro can be exported for the use within other crates. My be it can be exported as a feature?
At least, I didn't found any possibility to access the macro from an other crate.
The text was updated successfully, but these errors were encountered: