Skip to content

fix unstable issue ref for Unsize #28031

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

Merged
merged 1 commit into from
Aug 27, 2015
Merged

fix unstable issue ref for Unsize #28031

merged 1 commit into from
Aug 27, 2015

Conversation

durka
Copy link
Contributor

@durka durka commented Aug 26, 2015

It was pointing at the issue for placement_new_protocol.

It was pointing at the issue for `placement_new_protocol`.
@rust-highfive
Copy link
Contributor

r? @alexcrichton

(rust_highfive has picked a reviewer for you, use r? to override)

@alexcrichton
Copy link
Member

@bors: r+ 2367caf

Oops, thanks!

@durka
Copy link
Contributor Author

durka commented Aug 27, 2015

Huh, there are more. Will open another PR to fix the rest.

@bors
Copy link
Collaborator

bors commented Aug 27, 2015

⌛ Testing commit 2367caf with merge 79cd661...

@bors
Copy link
Collaborator

bors commented Aug 27, 2015

💔 Test failed - auto-linux-32-opt

@alexcrichton
Copy link
Member

@bors: retry

On Thu, Aug 27, 2015 at 7:32 AM, bors notifications@github.com wrote:

[image: 💔] Test failed - auto-linux-32-opt
http://buildbot.rust-lang.org/builders/auto-linux-32-opt/builds/6236


Reply to this email directly or view it on GitHub
#28031 (comment).

bors added a commit that referenced this pull request Aug 27, 2015
It was pointing at the issue for `placement_new_protocol`.
@bors
Copy link
Collaborator

bors commented Aug 27, 2015

⌛ Testing commit 2367caf with merge 17b6fcd...

@bors bors merged commit 2367caf into rust-lang:master Aug 27, 2015
bors added a commit that referenced this pull request Aug 28, 2015
After submitting #28031, I ran a [script](https://gist.github.com/durka/a5243440697c780f669b) on the rest of src/ and found some anomalies. In this PR are the fixes that I thought were obvious (but I might be wrong!). The others I've submitted in issue #28037.
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.

4 participants