diff options
| author | bors <bors@rust-lang.org> | 2016-07-17 09:07:50 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-07-17 09:07:50 -0700 |
| commit | 34f35ed29c8acdbe1e3c172786fc41d6f4fb6090 (patch) | |
| tree | 0fb3f8e6ab198477b5015ba7cf05f5a3a63a1e6b /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 6aba7be9a67467d31e6cbf75dc8b5f44d60cb5ca (diff) | |
| parent | f66da5e7942954730fe19f8bba957759fa13984b (diff) | |
| download | rust-34f35ed29c8acdbe1e3c172786fc41d6f4fb6090.tar.gz rust-34f35ed29c8acdbe1e3c172786fc41d6f4fb6090.zip | |
Auto merge of #34871 - petrochenkov:inherent, r=jseyfried
Do not resolve inherent static methods from other crates prematurely Under some specific circumstances paths like `Type::method` can be resolved early in rustc_resolve instead of type checker. `Type` must be defined in another crate, it should be an enum or a trait object (i.e. a type that acts as a "module" in resolve), and `method` should be an inherent static method. As a result, such paths don't go through `resolve_ufcs`, may be resolved incorrectly and break some invariants in type checker. This patch removes special treatment of such methods. The removed code was introduced in https://github.com/rust-lang/rust/commit/2bd46e767c0fe5b6188df61cb9daf8f2e65a3ed0 to fix a problem that no longer exists. r? @jseyfried
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions