diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2025-09-30 22:25:17 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-30 22:25:17 +1000 |
| commit | 156d150381ab2e5f2dc2c78eb83b76d7ae95733c (patch) | |
| tree | 7baa92df10a96832d5a5f2dd8496aab251f03164 /src | |
| parent | 5a6ac8c322a95e9607d7dc9f5760a60ff44d2c9a (diff) | |
| parent | 66b664c9961e54282fbaccef72f90dfa7dd1418f (diff) | |
| download | rust-156d150381ab2e5f2dc2c78eb83b76d7ae95733c.tar.gz rust-156d150381ab2e5f2dc2c78eb83b76d7ae95733c.zip | |
Rollup merge of #147109 - BoxyUwU:rename_concrete_opaques, r=lcnr
Rename various "concrete opaque type" things to say "hidden type" r? lcnr I've found "concrete opaque type" terminology to be somewhat confusing as in conversation and when explaining opaque type stuff to people I always just talk about things in terms of hidden types. Also the hidden types of opaques are very much not *concrete* in the same sense that a type without any generic parameters is concrete which is an unfortunate overlap in terminology. I've tried to update comments to also stop referring to things as concrete opaque types but this is mostly best effort as it difficult to find all such cases amongst the massive amounts of uses of "concrete" or "hidden" across the whole compiler.
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions