-
-
Notifications
You must be signed in to change notification settings - Fork 15k
logging functions handle unicode poorly #2154
Copy link
Copy link
Closed
Labels
A-UnicodeArea: UnicodeArea: UnicodeA-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsC-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.
Metadata
Metadata
Assignees
Labels
A-UnicodeArea: UnicodeArea: UnicodeA-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsC-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.
Type
Fields
Give feedbackNo fields configured for issues without a type.
If I log a string with unicode I would like to see the unicode not some wacky utf-8 multi-byte escape sequence. Here is a test case:
// Run with
export RUST_LOG=test && ./testimport io;
fn is_print(ch: char) -> bool
{
ret ch >= '_' && ch <= '~';
}
fn munge_chars(chars: [char]) -> str
{
let bullet = '\u2022';
}
fn main()
{
let s = munge_chars(['h', 'e', 'l', 'l', 'o', '\u0003']);
}