-
Notifications
You must be signed in to change notification settings - Fork 550
Document lang items #1119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document lang items #1119
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,41 @@ | ||||||
# Lang items | ||||||
|
||||||
The compiler has certain pluggable operations, that is, functionality that isn't hard-coded into | ||||||
the language, but is implemented in libraries, with a special marker to tell the compiler it | ||||||
exists. The marker is the attribute `#[lang = "..."]` and there are various different values of | ||||||
jyn514 marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
`...`, i.e. various different 'lang items'. | ||||||
|
||||||
Many such lang items can be implemented only in one sensible way, such as `add` (`trait | ||||||
core::ops::Add`) or `future_trait` (`trait core::future::Future`). Others can be overriden to | ||||||
achieve some specific goals; for example, you can control your binary's entrypoint. | ||||||
|
||||||
Features provided by lang items include: | ||||||
|
||||||
- overloadable operators via traits: the traits corresponding to the | ||||||
`==`, `<`, dereferencing (`*`) and `+` (etc.) operators are all | ||||||
jyn514 marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
marked with lang items; those specific four are `eq`, `ord`, | ||||||
`deref`, and `add` respectively. | ||||||
- stack unwinding and general failure; the `eh_personality`, `panic` and | ||||||
jyn514 marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
`panic_bounds_checks` lang items. | ||||||
- the traits in `std::marker` used to indicate properties of types used by the compiler; | ||||||
lang items `send`, `sync` and `copy`. | ||||||
- the special marker types used for variance indicators found in | ||||||
`core::marker`; lang item `phantom_data`. | ||||||
|
||||||
Lang items are loaded lazily by the compiler; e.g. if one never uses `Box` | ||||||
then there is no need to define functions for `exchange_malloc` and | ||||||
`box_free`. `rustc` will emit an error when an item is needed but not found | ||||||
in the current crate or any that it depends on. | ||||||
|
||||||
Most lang items are defined by `libcore`, but if you're trying to build an | ||||||
executable with `#![no_std]`, you'll run into the need for lang items. | ||||||
jyn514 marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
## List of all language items | ||||||
|
||||||
You can find language items in the following places: | ||||||
- An exhaustive reference in the compiler documentation: [`rustc_hir::LangItem`] | ||||||
- An auto-generated list with source locations by using ripgrep: `rg '#\[.*lang =' library/` | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think this is more clear. I could say "A list of items in the standard library, along with their sources, by using ripgrep" if you like. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I suggested that just to make it clear that language items can be defined outside of the standard library, and that these source locations are specifically the ones defined by the standard library. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think that's too much nuance to pack into 4 words. Defining lang-items outside the standard library is pretty rare - I can add a section if you like, but I don't think it belongs here. |
||||||
|
||||||
Note that language items are explicitly unstable and may change in any new release. | ||||||
|
||||||
[`rustc_hir::LangItem`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/lang_items/enum.LangItem.html |
Uh oh!
There was an error while loading. Please reload this page.