Skip to content
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

Remove incorrect documentation and assume pointer is not null in GlobalAlloc::dealloc #144

Merged
merged 3 commits into from
Dec 11, 2019
Merged

Conversation

davidMcneil
Copy link
Contributor

@davidMcneil davidMcneil commented Dec 11, 2019

Resolves #143

@@ -366,8 +366,6 @@ extern "C" {
///
/// This makes the space available for future allocations.
///
/// If `ptr` is null, no action occurs.
///
/// # Safety
///
/// The behavior is _undefined_ if:
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We probably need to add to these lists that the behavior is undefined if the pointer is null in both cases.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed in ffdcf7

Signed-off-by: David McNeil <[email protected]>
@gnzlbg gnzlbg merged commit c27a859 into gnzlbg:master Dec 11, 2019
@gnzlbg
Copy link
Owner

gnzlbg commented Dec 11, 2019

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Is sdallocx safe to call with a null pointer?
2 participants