]> git.lizzy.rs Git - rust.git/commit
projects / rust.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(merge: ecbd8c3 b3e1aca)
Auto merge of #28504 - Eljay:fix-trait-privacy, r=nrc
authorbors <bors@rust-lang.org>
Tue, 22 Sep 2015 22:42:00 +0000 (22:42 +0000)
committerbors <bors@rust-lang.org>
Tue, 22 Sep 2015 22:42:00 +0000 (22:42 +0000)
commitad82e0ac180deef65b5757a6e4d7fa79aab5521a
tree9ccf7a87c2fb357ecc0c238c2663dcc56688f648tree | snapshot
parentecbd8c3b43d7d992938f7214b3bab1c017669e59commit | diff
parentb3e1aca40f889a565bfa2607b82b80fe7cbcefeacommit | diff
Auto merge of #28504 - Eljay:fix-trait-privacy, r=nrc

Fixes #16264 / #18241.

As far as I can tell, it should be impossible for a trait to be inaccessible if it's in scope, so this check is unnecessary. Are there any cases where this check is actually needed?
src/librustc_privacy/lib.rs diff1 | diff2 | blob | history
Empowering everyone to build reliable and efficient software.