Skip to content

Commit 443bf93

Browse files
committed
Fix a typo in the ifmt dox
1 parent 783c6a1 commit 443bf93

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

src/libstd/fmt/mod.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ string.
9393
Because formatting is done via traits, there is no requirement that the
9494
`d` format actually takes an `int`, but rather it simply requires a type which
9595
ascribes to the `Signed` formatting trait. There are various parameters which do
96-
require a particular type, however. Namely if the sytnax `{:.*s}` is used, then
96+
require a particular type, however. Namely if the syntax `{:.*s}` is used, then
9797
the number of characters to print from the string precedes the actual string and
9898
must have the type `uint`. Although a `uint` can be printed with `{:u}`, it is
9999
illegal to reference an argument as such. For example, this is another invalid

src/test/auxiliary/iss.rs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313
// part of issue-6919.rs
1414

1515
struct C<'self> {
16-
pub k: &'self fn(),
16+
k: &'self fn(),
1717
}
1818

1919
fn no_op() { }

src/test/run-pass/issue-6898.rs

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,18 +21,18 @@ pub fn size_of_val<T>(val: &T) -> uint {
2121
}
2222

2323
pub trait TypeInfo {
24-
pub fn size_of() -> uint;
25-
pub fn size_of_val(&self) -> uint;
24+
fn size_of() -> uint;
25+
fn size_of_val(&self) -> uint;
2626
}
2727

2828
impl<T> TypeInfo for T {
2929
/// The size of the type in bytes.
30-
pub fn size_of() -> uint {
30+
fn size_of() -> uint {
3131
unsafe { intrinsics::size_of::<T>() }
3232
}
3333

3434
/// Returns the size of the type of `self` in bytes.
35-
pub fn size_of_val(&self) -> uint {
35+
fn size_of_val(&self) -> uint {
3636
TypeInfo::size_of::<T>()
3737
}
3838
}

0 commit comments

Comments
 (0)