-
Notifications
You must be signed in to change notification settings - Fork 139
Rename MultiUseSandbox
-> Sandbox
, UninitializedSandbox::evolve
-> UninitializedSandbox::init
#762
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
base: main
Are you sure you want to change the base?
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.
Lgtm. I am thinking we might want to take this chance to do other breaking changes such as determining which module Sandbox
belongs to, and whether or not we want to any re-exports of Sandbox
at all.
@@ -74,7 +74,7 @@ pub use error::HyperlightError; | |||
/// Re-export for `MemMgrWrapper` type | |||
/// A sandbox that can call be used to make multiple calls to guest functions, | |||
/// and otherwise reused multiple times | |||
pub use sandbox::MultiUseSandbox; |
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.
Maybe we can take this chance to remove these reexports? I'm not sure there is a reason to keep these?
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.
I opened #765 to see what we want to expose as our public API
Signed-off-by: Jorge Prendes <[email protected]>
Signed-off-by: Jorge Prendes <[email protected]>
Signed-off-by: Jorge Prendes <[email protected]>
Signed-off-by: Jorge Prendes <[email protected]>
Signed-off-by: Jorge Prendes <[email protected]>
Rename
MultiUseSandbox
asSandbox
.Rename
UninitializedSandbox::evolve
asUninitializedSandbox::init