Glossary

[mark-i-m]

Are there any other terms that should be added to the glossary? Please make suggestions.

• filemap (What are "filemaps"? #35)
• soundness (Add soundness and completeness to glossary #54)
• completeness (Add soundness and completeness to glossary #54)
• skolemization (rework and vastly expand the MIR section #67)
• sigil (Add a few more terms to the glossary #57)
• LTO, ThinLTO, FatLTO (Add some codegen related terminology to glossary #56)
• TLS (Add some codegen related terminology to glossary #56)
• LLVM (Add some codegen related terminology to glossary #56)
• IR (Add some codegen related terminology to glossary #56)
• Fat pointer (Add definitions of fat, double, and wide pointers #112)
• region (Add a few more terms to the glossary #57)
• HIR map (Add HIR MAP to glossary #63)
• CTFE (compile-time function evaluation)... This just needs a link to the const eval/miri sections (add a bunch of type-related terms to glossary (and few others) #152)
• rib (see name resolution chapter) (add a bunch of type-related terms to glossary (and few others) #152)
• upvar (I believe an "upvar" is just a variable captured by a closure) (add a bunch of type-related terms to glossary (and few others) #152)
• early-bound lifetime (Add various terms to the glossary #281)
• interned (Add various terms to the glossary #281)
• item (Add various terms to the glossary #281)
• late-bound lifetime (Add various terms to the glossary #281)
• lang item (Add various terms to the glossary #281)
• memoized (Add various terms to the glossary #281)
• string interning (Add various terms to the glossary #281)
• drop glue (Add various terms to the glossary #281)
• late-bound regions/lifetimes (Add various terms to the glossary #281)
• gensym
• landing pad
• skolemization leak

[phansch]

One thing I have been wondering is if 'soundness' means something special in the compiler context or if it is just a different word for correctness. There are lot's of issues mentioning 'soundness bugs' and 'soundness fixes'. So maybe it makes sense to add this too or explain it somewhere?

[mark-i-m]

Yes, soundness is a technical term in programming languages literature. You will usually read about proving "soundness" and "completeness".

Roughly, IIRC, soundness means that if a program type-checks, it is type-safe; i.e. I can never (in safe rust) force a value into a variable if the wrong type. Completeness means that every type-safe program also type-checks. Having both is very hard, and usually soundness is more important.

[samWson]

I've found a good definition of Fat Pointers in the Programming Rust book. I can enter that in the glossary this weekend if it's OK with you team.

[steveklabnik]

We've been using "double pointer" or "wide pointer" as well; might be worth considering as "double pointer" at least is significantly more descriptive, IMO.

[hanna-kruppe]

FWIW "double pointer" can also be read as "pointer-to-pointer" (and I've definitely seen it used in that sense in other languages). Besides, double becomes inaccurate with custom DSTs (which can add more data than just one word to the pointer). One precise and universal phrase is "pointer with metadata" but that's probably a bit too verbose.

[samWson]

"Pointer with metadata" is what I've found the definition of a fat pointer to be. A two word value with an address and some extra information needed to put the value to use.

[mark-i-m]

I think we could add all of these terms to the glossary.

[samWson]

Is this a case with of several phrases with the same meaning? Or are these the names of different things?

[mark-i-m]

I believe "fat pointer", "wide pointer", and "double pointer" are all intended to be synonyms.