diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2025-06-01 19:35:42 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-06-01 19:35:42 +0200 |
| commit | 335232d958b235c8e695ee67c7fee997917621f1 (patch) | |
| tree | 6223d20de9bda9403a0f928dd927132e09d30719 /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | cd0adc9d7b2a2c7a41df53d6a384a42fbe2fce21 (diff) | |
| parent | f388c987cf5bab0b4beea85ba2e326c525f07034 (diff) | |
| download | rust-335232d958b235c8e695ee67c7fee997917621f1.tar.gz rust-335232d958b235c8e695ee67c7fee997917621f1.zip | |
Rollup merge of #141224 - RalfJung:no-objects, r=traviscross
terminology: allocated object → allocation Rust does not have "objects" in memory so "allocated object" is a somewhat odd name. I am not sure where the term comes from. "object" has been used to refer to allocations already [in 1.0 docs](https://doc.rust-lang.org/1.0.0/std/primitive.pointer.html#method.offset); this was apparently later changed to "allocated object". "Allocation" is already the terminology used in Miri and in the [UCG](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#allocation). We should properly move to that terminology, and avoid any confusion about whether Rust has an object memory model. (It does not. Memory contains untyped bytes.) Cc ``@rust-lang/opsem`` ``@rust-lang/lang``
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions