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

Tweak wording of copy_nonoverlapping_memory to remove misleading 'allocated'. #22164

Merged
merged 1 commit into from
Feb 12, 2015

Conversation

huonw
Copy link
Member

@huonw huonw commented Feb 11, 2015

It doesn't have to be a literal memory allocation (ala malloc), e.g. it
can be in static memory, so saying "allocated" is mildly misleading.

Thanks to @mahkoh for pointing it out.

r? @steveklabnik

…ocated'.

It doesn't have to be a literal memory allocation (ala malloc), e.g. it
can be in static memory, so saying "allocated" is mildly misleading.
@steveklabnik
Copy link
Member

@bors: r+ d8d4761 rollup

@bors
Copy link
Collaborator

bors commented Feb 11, 2015

🙀 You have the wrong number! Please try again with d8d3761.

@steveklabnik
Copy link
Member

@bors: r+ d8d3761 rollup

richo added a commit to richo/rust that referenced this pull request Feb 11, 2015
It doesn't have to be a literal memory allocation (ala malloc), e.g. it
can be in static memory, so saying "allocated" is mildly misleading.

Thanks to @mahkoh for pointing it out.

r? @steveklabnik
alexcrichton added a commit to alexcrichton/rust that referenced this pull request Feb 11, 2015
It doesn't have to be a literal memory allocation (ala malloc), e.g. it
can be in static memory, so saying "allocated" is mildly misleading.

Thanks to @mahkoh for pointing it out.

r? @steveklabnik
@bors bors merged commit d8d3761 into rust-lang:master Feb 12, 2015
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.

3 participants