about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc/example/alloc_example.rs
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2021-11-10 18:52:28 +0100
committerGitHub <noreply@github.com>2021-11-10 18:52:28 +0100
commitb31f0198b14300d232dc1b6d1f52dc92da7818ff (patch)
treea3a7cface2d874cb785cdee72d57033afdeb43f9 /compiler/rustc_codegen_gcc/example/alloc_example.rs
parent858fea410d89986669c3613c63b5401abd72b891 (diff)
parent8d5ef320fc6c2d4436692d1558d36bd59c49394b (diff)
downloadrust-b31f0198b14300d232dc1b6d1f52dc92da7818ff.tar.gz
rust-b31f0198b14300d232dc1b6d1f52dc92da7818ff.zip
Rollup merge of #90727 - GuillaumeGomez:remove-potential-useless-search-index-data, r=notriddle,camelid
Remove potential useless data for search index

I uncovered this case when working on https://github.com/rust-lang/rust/pull/90726 to debug https://github.com/rust-lang/rust/pull/90385.

Explanations: if we have a full generic, we check if it has generics then we do the following:
 * If it has only one generic, we remove one nested level in order to not keep the "parent" generic (since it has empty name, it's useless after all).
 * Otherwise we add it alongside its generics.

However, I didn't handle the case where a generic had no generics. Meaning that we were adding items with empty names in the search index. So basically useless data in the search index.

r? `@camelid`
Diffstat (limited to 'compiler/rustc_codegen_gcc/example/alloc_example.rs')
0 files changed, 0 insertions, 0 deletions