Skip to content

Remove ty_open. #22213

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 3 commits into from
Feb 24, 2015
Merged

Remove ty_open. #22213

merged 3 commits into from
Feb 24, 2015

Conversation

eddyb
Copy link
Member

@eddyb eddyb commented Feb 12, 2015

This type wasn't necessary, as there was no place using it and unsized types not wrapped in it, at the same time.
r? @nikomatsakis

@nikomatsakis
Copy link
Contributor

@eddyb r+ modulo comments, this seems nice overall (and @nick29581 mentioned he was fine with it too). But I'd like to understand what's going on with that change to type-needs-drop.

@eddyb eddyb force-pushed the ty_open-case-closed branch from 4893b3a to 258fa79 Compare February 17, 2015 18:29
@eddyb
Copy link
Member Author

eddyb commented Feb 17, 2015

@bors r=nikomatsakis 258fa79

@bors
Copy link
Collaborator

bors commented Feb 18, 2015

⌛ Testing commit 258fa79 with merge 6d44972...

@bors
Copy link
Collaborator

bors commented Feb 18, 2015

💔 Test failed - auto-mac-64-nopt-t

@eddyb
Copy link
Member Author

eddyb commented Feb 18, 2015

I was going to adjust the tests for the new errors, but it looks like that would be a regression.

I'm tempted to use something like the current debug location to always provide some span to functions like ty::type_is_sized which may need it. However, trans::common::type_is_sized could at most require a CrateContext, as it's used from Datum and type_of and at least the latter has to be usable from outside a FunctionContext.

A global "current Span" is too hacky for my taste but we mainly need that span for such _extra_ordinary overflow errors, and only to point to something better than "somewhere in this crate".
@nikomatsakis, what are your thoughts on this?

@nikomatsakis
Copy link
Contributor

@eddyb I personally think you can just adjust the tests. This is a pre-existing problem. I thought there was an issue for it, but I can't find it now. In any case, I think that in the end we should probably just thread a span down through typeof and so forth, though, annoying as that is.

@nikomatsakis
Copy link
Contributor

(We might want to open an issue and attach a FIXME in type_is_sized and on the tests.)

@eddyb
Copy link
Member Author

eddyb commented Feb 18, 2015

It's actually not coming from type_needs_drop so that means I forgot to run the compile-fail tests before that. In any case, if you don't mind a temporary loss of diagnostic information, I won't.

@eddyb eddyb force-pushed the ty_open-case-closed branch 2 times, most recently from a1f9fe6 to 85052b4 Compare February 19, 2015 00:12
@eddyb
Copy link
Member Author

eddyb commented Feb 19, 2015

@bors r=nikomatsakis 85052b4

@eddyb eddyb force-pushed the ty_open-case-closed branch 2 times, most recently from fd9b13b to 724c207 Compare February 20, 2015 17:25
@eddyb
Copy link
Member Author

eddyb commented Feb 20, 2015

@bors r=nikomatsakis 724c207

@bors
Copy link
Collaborator

bors commented Feb 21, 2015

⌛ Testing commit 724c207 with merge e6fdf5b...

@bors
Copy link
Collaborator

bors commented Feb 21, 2015

💔 Test failed - auto-mac-64-nopt-t

@Manishearth
Copy link
Member


failures:

---- [run-pass-valgrind] run-pass-valgrind/dst-dtor-1.rs stdout ----

error: test run failed!
status: exit code: 101
command: x86_64-apple-darwin/test/run-pass-valgrind/dst-dtor-1.stage2-x86_64-apple-darwin 
stdout:
------------------------------------------

------------------------------------------
stderr:
------------------------------------------
thread '<main>' panicked at 'assertion failed: DROP_RAN', /Users/rustbuild/src/rust-buildbot/slave/auto-mac-64-nopt-t/build/src/test/run-pass-valgrind/dst-dtor-1.rs:34

------------------------------------------

thread '[run-pass-valgrind] run-pass-valgrind/dst-dtor-1.rs' panicked at 'explicit panic', /Users/rustbuild/src/rust-buildbot/slave/auto-mac-64-nopt-t/build/src/compiletest/runtest.rs:1466


---- [run-pass-valgrind] run-pass-valgrind/dst-dtor-2.rs stdout ----

error: test run failed!
status: exit code: 101
command: x86_64-apple-darwin/test/run-pass-valgrind/dst-dtor-2.stage2-x86_64-apple-darwin 
stdout:
------------------------------------------

------------------------------------------
stderr:
------------------------------------------
thread '<main>' panicked at 'assertion failed: DROP_RAN == 3', /Users/rustbuild/src/rust-buildbot/slave/auto-mac-64-nopt-t/build/src/test/run-pass-valgrind/dst-dtor-2.rs:31

------------------------------------------

thread '[run-pass-valgrind] run-pass-valgrind/dst-dtor-2.rs' panicked at 'explicit panic', /Users/rustbuild/src/rust-buildbot/slave/auto-mac-64-nopt-t/build/src/compiletest/runtest.rs:1466

@eddyb eddyb force-pushed the ty_open-case-closed branch from 724c207 to 8659de0 Compare February 24, 2015 06:40
@eddyb
Copy link
Member Author

eddyb commented Feb 24, 2015

@bors r=nikomatsakis 8659de0

@Manishearth
Copy link
Member

@bors: p=10

@Manishearth
Copy link
Member

Mostly everything else will come in the rollup.

@Manishearth
Copy link
Member

@bors: p=5

Manishearth added a commit to Manishearth/rust that referenced this pull request Feb 24, 2015
…tsakis

 This type wasn't necessary, as there was no place using it and unsized types not wrapped in it, at the same time.
r? @nikomatsakis
Manishearth added a commit to Manishearth/rust that referenced this pull request Feb 24, 2015
@bors bors merged commit 8659de0 into rust-lang:master Feb 24, 2015
@eddyb eddyb deleted the ty_open-case-closed branch February 24, 2015 12:47
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