diff options
| author | Dylan DPC <dylan.dpc@gmail.com> | 2021-03-31 01:14:40 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-03-31 01:14:40 +0200 |
| commit | 7391124154094b9177e0448026aa0d6dd5c1a48a (patch) | |
| tree | ddafc24c97b8b349cf5e9b01067b648f0f941abe /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | 74874a690bc95443292496ff5df5cc5c8cb56e0b (diff) | |
| parent | 761296bcb37f4099921c064137353762ae5ddf3f (diff) | |
| download | rust-7391124154094b9177e0448026aa0d6dd5c1a48a.tar.gz rust-7391124154094b9177e0448026aa0d6dd5c1a48a.zip | |
Rollup merge of #80720 - steffahn:prettify_prelude_imports, r=camelid,jyn514
Make documentation of which items the prelude exports more readable.
I recently figured out that rustdoc allows link inside of inline code blocks as long as they’re delimited with `<code> </code>` instead of `` ` ` ``. I think this applies nicely in the listing of prelude exports [in the docs](https://doc.rust-lang.org/std/prelude/index.html). There, currently unformatted `::` and `{ , }` is used in order to mimick import syntax while attatching links to individual identifiers.
## Rendered Comparison
### Currently (light)

### After this PR (light)

### Currently (dark)

### After this PR (dark)

### Currently (ayu)

### After this PR (ayu)

_Edit:_ I just noticed, the “current” screenshots are from stable, so there are a few more differences in the pictures than the ones from just this PR.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
