mathieu/granite-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Support #fmt precision for bools, with same rules as strings

Browse source 
Not totally confident this is desirable. The alternative would be to make it a
compile error.
This commit is contained in:
Brian Anderson 2011-04-17 17:24:17 -04:00
parent da996d6e6b
commit 1bec738c56
2 changed files with 14 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
src/lib/ExtFmt.rs
View file

@ -358,11 +358,15 @@ mod RT {
}
fn conv_bool(&conv cv, bool b) -> str {
auto s;
if (b) {
ret pad(cv, "true");
s = "true";
} else {
ret pad(cv, "false");
s = "false";
}
// Run the boolean conversion through the string conversion logic,
// giving it the same rules for precision, etc.
ret conv_str(cv, s);
}
fn conv_char(&conv cv, char c) -> str {

8
src/test/run-pass/syntax-extension-fmt.rs
View file

@ -104,4 +104,12 @@ fn main() {
test(#fmt("%.5x", 127u), "0007f");
test(#fmt("%.5t", 3u), "00011");
test(#fmt("%.5c", 'A'), "A");
// Bool precision. I'm not sure if it's good or bad to have bool
// conversions support precision - it's not standard printf so we
// can do whatever. For now I'm making it behave the same as string
// conversions.
test(#fmt("%.b", true), "");
test(#fmt("%.0b", true), "");
test(#fmt("%.1b", true), "t");
}