-
Notifications
You must be signed in to change notification settings - Fork 11
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
Build without sandboxing on Windows #1485
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.
I like the choice of making this a platform-specific thing rather than a feature, makes it more about not being possible rather than making it sound like sandboxing is a feature you might want to disable in certain scenarios.
I've got one minor nit but I'm fine with it going either way.
I'm still reviewing...but there are three warnings on the Windows job. Do those need to be accounted for here? If so, then enabling warnings as errors should also be pursued. |
They're pretty simple to handle, so sure.
This might just anger people... So I'd rather not do that for now. |
Roger that. Maybe case in point...there are two new warnings now. |
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
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.
One change requested.
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
With this patch, all sandboxing code is guarded by
#[cfg(unix)]
.