diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2023-07-28 19:51:14 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-07-28 19:51:14 +0200 |
| commit | a1fb86144da900cded8e82598a60cce589c7fbcd (patch) | |
| tree | c8cd0253576ce0822f16aea17b05102c0731b0fc /compiler/rustc_codegen_gcc | |
| parent | 317ec04d18ab9c5d09a4d9b4418a12da8974b961 (diff) | |
| parent | e051a323110d438c337f3f893d171fade7d2d1a6 (diff) | |
| download | rust-a1fb86144da900cded8e82598a60cce589c7fbcd.tar.gz rust-a1fb86144da900cded8e82598a60cce589c7fbcd.zip | |
Rollup merge of #114099 - davidtwco:issue-113860-staged-api-effective-vis-gt-nominal-vis-when-trait-method-vis, r=petrochenkov
privacy: no nominal visibility for assoc fns Fixes #113860. When `staged_api` is enabled, effective visibilities are computed earlier and this can trigger an ICE in some cases. In particular, if a impl of a trait method has a visibility then an error will be reported for that, but when privacy invariants are being checked, the effective visibility will still be greater than the nominal visbility and that will trigger a `span_bug!`. However, this invariant - that effective visibilites are limited to nominal visibility - doesn't make sense for associated functions.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions