You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v1.58 introduces captured identifiers in format strings, and yet it seems most of the examples in the book still use positional placeholders. Is this intentional, or should I submit a pull request modifying some of those usages? Thx!
The text was updated successfully, but these errors were encountered:
nyurik
added a commit
to nyurik/book
that referenced
this issue
Feb 6, 2022
Per rust-lang#3047, use captured identifiers instead of the positional ones for some examples, e.g.
```diff
- println!("Worker {} got a job; executing.", id);
+ println!("Worker {id} got a job; executing.");
```
Per rust-lang#3047, use captured identifiers instead of the positional ones for some examples, e.g.
```diff
- println!("Worker {} got a job; executing.", id);
+ println!("Worker {id} got a job; executing.");
```
nyurik
added a commit
to nyurik/book
that referenced
this issue
Oct 30, 2023
Per rust-lang#3047, use captured identifiers instead of the positional ones for some examples, e.g.
```diff
- println!("Worker {} got a job; executing.", id);
+ println!("Worker {id} got a job; executing.");
```
v1.58 introduces captured identifiers in format strings, and yet it seems most of the examples in the book still use positional placeholders. Is this intentional, or should I submit a pull request modifying some of those usages? Thx!
The text was updated successfully, but these errors were encountered: