Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Closed
Changes from 1 commit
Commits
Show all changes
57 commits
Select commit Hold shift + click to select a range
a87b44d
Always inline `mem::{size_of,align_of}` in debug builds
tesuji Oct 2, 2019
3b0fd82
Disable Go and OCaml bindings when building LLVM
tmiasko Oct 8, 2019
e6ce3ef
Collect occurrences of for mismatched braces diagnostic
XiangQingW Oct 13, 2019
888d0ba
Collect occurrences of for mismatched braces diagnostic
XiangQingW Oct 13, 2019
77f0aaf
Add more coherence tests
weiznich Oct 12, 2019
fe819a0
Collect occurrences of for mismatched braces diagnostic
XiangQingW Oct 13, 2019
10236f1
Add long error explanation for E0577
GuillaumeGomez Oct 15, 2019
3d88f2c
Update ui tests
GuillaumeGomez Oct 15, 2019
70b136d
Use a `BitSet` in `LexicalResolver::iterate_until_fixed_point()`.
nnethercote Oct 15, 2019
d51fee0
Inline and remove `iterate_until_fixed_point()`.
nnethercote Oct 16, 2019
42c0236
Use a sharded dep node to dep node index map
Zoxc Jun 13, 2019
c716be6
show up some extra info when t!() fails
Oct 17, 2019
83e97c6
properly document panics in div_euclid and rem_euclid
tspiteri Oct 17, 2019
e417180
Update error_codes.rs
Dylan-DPC Oct 17, 2019
a4d9492
add option to ping llvm ice-breakers to triagebot
nikomatsakis Oct 17, 2019
5fe88ab
save-analysis: Nest tables when processing impl items
Xanewok Oct 17, 2019
ad6ce46
save-analysis: Add a relevant test case
Xanewok Oct 17, 2019
4e6efe4
reorder fmt docs for more clarity
RalfJung Oct 17, 2019
5487994
Update triagebot.toml
nikomatsakis Oct 17, 2019
c0b7e76
example for padding any format
RalfJung Oct 17, 2019
c9b27d1
doc: make BitSet intro more short
tshepang Oct 17, 2019
5de9cb0
super_ty on MutVisitor is empty so avoid the call
spastorino Oct 7, 2019
e069e9c
Prepare promote_consts MutVisitor to have projections interned
spastorino Oct 7, 2019
591cc9a
Prepare simplify MutVisitor to have projections interned
spastorino Oct 7, 2019
bb7d6d1
Prepare renumber MutVisitor to have projections interned
spastorino Oct 7, 2019
e3e9951
Prepare inline MutVisitor to have projections interned
spastorino Oct 7, 2019
0fc063f
Prepare generator MutVisitor to have projections interned
spastorino Oct 7, 2019
39c9ed3
Prepare erase_regions MutVisitor to have projections interned
spastorino Oct 7, 2019
2b2e35b
Prepare def_use MutVisitor to have projections interned
spastorino Oct 8, 2019
4f2a110
Remove unneeded callback and just use the new_local value
spastorino Oct 8, 2019
7fa3425
Setup a different visit place set of methods for mutable and immutabl…
spastorino Oct 8, 2019
d53fc9c
Add process_* place hooks to improve code reutilization
spastorino Oct 8, 2019
d0eaf60
Remove two no-op `into()` calls.
nnethercote Oct 15, 2019
a6eef29
Make `TokenStream::from_iter` less general and more efficient.
nnethercote Oct 13, 2019
212ae58
Change `Lit::tokens()` to `Lit::token_tree()`.
nnethercote Oct 14, 2019
e4ec4a6
Change `MetaItem::tokens()` to `MetaItem::token_trees_and_joints()`.
nnethercote Oct 14, 2019
769e75b
Fix left/right shift typo in wrapping rotate docs
t-rapp Oct 18, 2019
4e3f4ca
Update error_codes.rs
Dylan-DPC Oct 18, 2019
9617014
Clarify diagnostics when using `~` as a unary op
JohnTitor Oct 18, 2019
4834996
Use Cow to handle modifications of projection in preparation for inte…
spastorino Oct 9, 2019
13e47c8
Rollup merge of #65016 - lzutao:inline-mem-constfn, r=oli-obk
tmandry Oct 18, 2019
53ba12c
Rollup merge of #65197 - spastorino:place-mut-visitor-adjusts2, r=oli…
tmandry Oct 18, 2019
739dd55
Rollup merge of #65201 - tmiasko:no-bindings, r=rkruppe
tmandry Oct 18, 2019
c3eaee3
Rollup merge of #65364 - XiangQingW:master, r=estebank
tmandry Oct 18, 2019
0e01e9d
Rollup merge of #65417 - weiznich:more_coherence_tests, r=nikomatsakis
tmandry Oct 18, 2019
f859526
Rollup merge of #65434 - GuillaumeGomez:long-err-explanation-E0577, r…
tmandry Oct 18, 2019
44acb1d
Rollup merge of #65455 - nnethercote:avoid-unnecessary-TokenTree-to-T…
tmandry Oct 18, 2019
809b3f0
Rollup merge of #65472 - Zoxc:sharded-dep-graph-2, r=nikomatsakis
tmandry Oct 18, 2019
4a76e6d
Rollup merge of #65480 - nnethercote:rm-iterate_until_fixed_size, r=n…
tmandry Oct 18, 2019
5221f28
Rollup merge of #65496 - tspiteri:euc-div-panic, r=KodrAus
tmandry Oct 18, 2019
f58b532
Rollup merge of #65508 - rust-lang:llvm-icebreakers-ping-1, r=simulacrum
tmandry Oct 18, 2019
00427cb
Rollup merge of #65511 - Xanewok:sa-nest-in-impls, r=pnkfelix
tmandry Oct 18, 2019
24e882e
Rollup merge of #65513 - RalfJung:fmt, r=Mark-Simulacrum
tmandry Oct 18, 2019
f1b0713
Rollup merge of #65532 - tshepang:shorten-intro, r=Dylan-DPC
tmandry Oct 18, 2019
6c2ab85
Rollup merge of #65540 - guanqun:extend-t-macro, r=nikomatsakis
tmandry Oct 18, 2019
236e53a
Rollup merge of #65549 - t-rapp:tr-wrapping-rotate-docs, r=jonas-schi…
tmandry Oct 18, 2019
12d1f86
Rollup merge of #65552 - JohnTitor:use-bitwise-not, r=Dylan-DPC
tmandry Oct 18, 2019
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
reorder fmt docs for more clarity
  • Loading branch information
RalfJung committed Oct 17, 2019
commit 4e6efe48110a5e09ee87b0aa8cea31d511bb5708
103 changes: 61 additions & 42 deletions src/liballoc/fmt.rs
Original file line number Diff line number Diff line change
Expand Up @@ -86,18 +86,53 @@
//! parameters (corresponding to `format_spec` in the syntax above). These
//! parameters affect the string representation of what's being formatted.
//!
//! ## Width
//!
//! ```
//! // All of these print "Hello x !"
//! println!("Hello {:5}!", "x");
//! println!("Hello {:1$}!", "x", 5);
//! println!("Hello {1:0$}!", 5, "x");
//! println!("Hello {:width$}!", "x", width = 5);
//! ```
//!
//! This is a parameter for the "minimum width" that the format should take up.
//! If the value's string does not fill up this many characters, then the
//! padding specified by fill/alignment will be used to take up the required
//! space (see below).
//!
//! The value for the width can also be provided as a [`usize`] in the list of
//! parameters by adding a postfix `$`, indicating that the second argument is
//! a [`usize`] specifying the width.
//!
//! Referring to an argument with the dollar syntax does not affect the "next
//! argument" counter, so it's usually a good idea to refer to arguments by
//! position, or use named arguments.
//!
//! ## Fill/Alignment
//!
//! The fill character is provided normally in conjunction with the
//! [`width`](#width)
//! parameter. This indicates that if the value being formatted is smaller than
//! `width` some extra characters will be printed around it. The extra
//! characters are specified by `fill`, and the alignment can be one of the
//! following options:
//! ```
//! assert_eq!(format!("Hello {:<5}!", "x"), "Hello x !");
//! assert_eq!(format!("Hello {:-<5}!", "x"), "Hello x----!");
//! assert_eq!(format!("Hello {:^5}!", "x"), "Hello x !");
//! assert_eq!(format!("Hello {:>5}!", "x"), "Hello x!");
//! ```
//!
//! The optional fill character and alignment is provided normally in conjunction with the
//! [`width`](#width) parameter. It must be defined before `width`, right after the `:`.
//! This indicates that if the value being formatted is smaller than
//! `width` some extra characters will be printed around it.
//! Filling comes in the following variants for different alignments:
//!
//! * `<` - the argument is left-aligned in `width` columns
//! * `^` - the argument is center-aligned in `width` columns
//! * `>` - the argument is right-aligned in `width` columns
//! * `[fill]<` - the argument is left-aligned in `width` columns
//! * `[fill]^` - the argument is center-aligned in `width` columns
//! * `[fill]>` - the argument is right-aligned in `width` columns
//!
//! The default [fill/alignment](#fillalignment) for non-numerics is a space and
//! left-aligned. The
//! defaults for numeric formatters is also a space but with right-alignment. If
//! the `0` flag (see below) is specified for numerics, then the implicit fill character is
//! `0`.
//!
//! Note that alignment may not be implemented by some types. In particular, it
//! is not generally implemented for the `Debug` trait. A good way to ensure
Expand All @@ -106,7 +141,15 @@
//!
//! ## Sign/`#`/`0`
//!
//! These can all be interpreted as flags for a particular formatter.
//! ```
//! assert_eq!(format!("Hello {:+}!", 5), "Hello +5!");
//! assert_eq!(format!("{:#x}!", 27), "0x1b!");
//! assert_eq!(format!("Hello {:05}!", 5), "Hello 00005!");
//! assert_eq!(format!("Hello {:05}!", -5), "Hello -0005!");
//! assert_eq!(format!("{:#010x}!", 27), "0x0000001b!");
//! ```
//!
//! These are all flags altering the behavior of the formatter.
//!
//! * `+` - This is intended for numeric types and indicates that the sign
//! should always be printed. Positive signs are never printed by
Expand All @@ -121,44 +164,15 @@
//! * `#X` - precedes the argument with a `0x`
//! * `#b` - precedes the argument with a `0b`
//! * `#o` - precedes the argument with a `0o`
//! * `0` - This is used to indicate for integer formats that the padding should
//! * `0` - This is used to indicate for integer formats that the padding to `width` should
//! both be done with a `0` character as well as be sign-aware. A format
//! like `{:08}` would yield `00000001` for the integer `1`, while the
//! same format would yield `-0000001` for the integer `-1`. Notice that
//! the negative version has one fewer zero than the positive version.
//! Note that padding zeroes are always placed after the sign (if any)
//! and before the digits. When used together with the `#` flag, a similar
//! rule applies: padding zeroes are inserted after the prefix but before
//! the digits.
//!
//! ## Width
//!
//! This is a parameter for the "minimum width" that the format should take up.
//! If the value's string does not fill up this many characters, then the
//! padding specified by fill/alignment will be used to take up the required
//! space.
//!
//! The default [fill/alignment](#fillalignment) for non-numerics is a space and
//! left-aligned. The
//! defaults for numeric formatters is also a space but with right-alignment. If
//! the `0` flag is specified for numerics, then the implicit fill character is
//! `0`.
//!
//! The value for the width can also be provided as a [`usize`] in the list of
//! parameters by using the dollar syntax indicating that the second argument is
//! a [`usize`] specifying the width, for example:
//!
//! ```
//! // All of these print "Hello x !"
//! println!("Hello {:5}!", "x");
//! println!("Hello {:1$}!", "x", 5);
//! println!("Hello {1:0$}!", 5, "x");
//! println!("Hello {:width$}!", "x", width = 5);
//! ```
//!
//! Referring to an argument with the dollar syntax does not affect the "next
//! argument" counter, so it's usually a good idea to refer to arguments by
//! position, or use named arguments.
//! the digits. The prefix is included in the total width.
//!
//! ## Precision
//!
Expand Down Expand Up @@ -235,9 +249,14 @@
//! them with the same character. For example, the `{` character is escaped with
//! `{{` and the `}` character is escaped with `}}`.
//!
//! ```
//! assert_eq!(format!("Hello {{}}"), "Hello {}");
//! assert_eq!(format!("{{ Hello"), "{ Hello");
//! ```
//!
//! # Syntax
//!
//! To summarize, you can find the full grammar of format strings.
//! To summarize, here you can find the full grammar of format strings.
//! The syntax for the formatting language used is drawn from other languages,
//! so it should not be too alien. Arguments are formatted with Python-like
//! syntax, meaning that arguments are surrounded by `{}` instead of the C-like
Expand Down