diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2023-12-15 11:51:23 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-12-15 11:51:23 +0100 |
| commit | ec0008a915c3d27528a2df0eb420aed748b217f8 (patch) | |
| tree | a56142d8f4e578b4b6064df07c49084271f32387 /src/librustdoc/html/static/js/src-script.js | |
| parent | d253bf61ad38a59cc579aee688f81a06c31283d3 (diff) | |
| parent | 823148fa849eb9b6fb896a0ac1772a2be3bdb043 (diff) | |
| download | rust-ec0008a915c3d27528a2df0eb420aed748b217f8.tar.gz rust-ec0008a915c3d27528a2df0eb420aed748b217f8.zip | |
Rollup merge of #113091 - GuillaumeGomez:prevent-cfg-merge-reexport, r=rustdoc
Don't merge cfg and doc(cfg) attributes for re-exports Fixes #112881. ## Explanations When re-exporting things with different `cfg`s there are two things that can happen: * The re-export uses a subset of `cfg`s, this subset is sufficient so that the item will appear exactly with the subset * The re-export uses a non-subset of `cfg`s (e.g. like the example I posted just above where the re-export is ungated), if the non-subset `cfg`s are active (e.g. compiling that example on windows) then this will be a compile error as the item doesn't exist to re-export, if the subset `cfg`s are active it behaves like 1. ### Glob re-exports? **This only applies to non-glob inlined re-exports.** For glob re-exports the item may or may not exist to be re-exported (potentially the `cfg`s on the path up until the glob can be removed, and only `cfg`s on the globbed item itself matter), for non-inlined re-exports see https://github.com/rust-lang/rust/issues/85043. cc `@Nemo157` r? `@notriddle`
Diffstat (limited to 'src/librustdoc/html/static/js/src-script.js')
0 files changed, 0 insertions, 0 deletions
