about summary refs log tree commit diff
path: root/src/libstd/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorSteve Klabnik <steve@steveklabnik.com>2016-01-06 18:31:58 -0500
committerSteve Klabnik <steve@steveklabnik.com>2016-01-06 18:31:58 -0500
commitfcb1ccf8c0fba7c4c455b4567336036595e6ae44 (patch)
tree453fc0609b614e683719961d7e645b8d9f5ab83a /src/libstd/sys/unix/stack_overflow.rs
parenteb41060ce252abd24d81849c6cd53c8ae58e5037 (diff)
parentce6baa77fe0fb53166f91d38e5187618af9b164c (diff)
downloadrust-fcb1ccf8c0fba7c4c455b4567336036595e6ae44.tar.gz
rust-fcb1ccf8c0fba7c4c455b4567336036595e6ae44.zip
Rollup merge of #30727 - tbu-:pr_doc_escaped_newline, r=steveklabnik
Rust differs in that behavior from C: In C, the newline escapes are resolved
before anything else, and in Rust this depends on whether the backslash is
escaped itself.

A difference can be observed in the following two programs:

```c
int main()
{
	printf("\\
n\n");
	return 0;
}
```

```rust
fn main() {
	println!("\\
n");
}
```

The first program prints two newlines, the second one prints a backslash, a
newline, the latin character n and a final newline.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions