-
Notifications
You must be signed in to change notification settings - Fork 148
Re-export macros in hyperlight_guest_tracing #734
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 macros in hyperlight_guest_tracing #734
Conversation
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.
Why is macros optional? What are the circumstances where I would use tracing and not macros?
bf1069b
to
365c8ac
Compare
Signed-off-by: Doru Blânzeanu <[email protected]>
Signed-off-by: Doru Blânzeanu <[email protected]>
365c8ac
to
330dca0
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.
LGTM
if lit_str.value().is_empty() { | ||
return Err(input.error("trace message must not be empty")); | ||
} |
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.
question: Where did the "trace message must not be empty" check move to?
We would still need to publish both, as |
To be able to use the tracing functionality as a dependency for a guest, we need to publish the crates.
It would be best if we could only publish one crate:
hyperlight-guest-tracing
.This PR re-exports the macros in the
hyperlight-guest-tracing
crate fromhyperlight-guest-tracing-macro
crate so the users don't need to have two dependencies.TODO: Need to publish the crate when releasing.