Use `dbg!` instead of `println!` for simple debug prints #2478

mgeisler · 2024-11-28T14:11:37Z

Originally, we did not show stderr output from the Playground programs. This was fixed in #2397 and so we can finally start converting the trivial debug print statements to use dbg!.

Specifically, I'm thinking of the many print statements that look like this:

println!("a: {a:?}");

They can simply become

dbg!(a);

When doing this conversion, pay attention to any  lines before the code block. They were added to skip translation of the "a: {a:?}" string, but now that the string disappears, the skip directive should be cleaned up too.

The text was updated successfully, but these errors were encountered:

Reverts #2383 Since #2397 is merged, to align the goal in #2478, rollback this temp workaround.

egithinji · 2025-02-17T17:24:54Z

Hi @mgeisler , I can look into this.

Part of google#2478.

The `dbg!` macro, being deployed more widely in google#2478, shows the line number. But if we inject `#![allow(..)]\n` then the printed numbers do not match those in the textarea. It turns out that `\n` is not required!

@egithinji

The `dbg!` macro, being deployed more widely in #2478, shows the line number. But if we inject `#![allow(..)]\n` then the printed numbers do not match those in the textarea. It turns out that `\n` is not required! cc @egithinji

Part of google#2478 to clean up code blocks when all that is needed is a trivial debug print statement. In certain slides (8.1, 9.2, 9.3, 10.5) I've opted to retain the use of println! because dbg! makes it less readable. The dbg! macro uses pretty-printing by default and this results in a simple array such as the one in 8.1 being printed vertically instead of in one line.

Part of google#2478 to clean up code blocks when all that is needed is a trivial debug print statement. In certain slides (8.1, 9.2, 9.3, 10.5) I've opted to retain the use of println! because dbg! makes it less readable. The dbg! macro uses pretty-printing by default and this results in a simple array such as the one in 8.1 being printed vertically instead of a cleaner one-liner.

Part of google#2478 to clean up code blocks when all that is needed is a trivial debug print statement. As in the other related PRs, in some places I opted to stick to println! for better readability.

As mentioned in #2478, this cleans up the code blocks when all that is needed is a trivial debug print statement. Only making changes to Day 1 morning session so that I can get feedback before proceeding with the rest of the course. --------- Co-authored-by: Eric Githinji <[email protected]>

Part of #2478 to clean up code blocks when all that is needed is a trivial debug print statement. In certain slides (8.1, 9.2, 9.3, 10.5) I've opted to retain the use of println! because dbg! makes it less readable. The dbg! macro uses pretty-printing by default and this results in a simple array such as the one in 8.1 being printed vertically instead of a cleaner one-liner. Co-authored-by: Eric Githinji <[email protected]>

As mentioned in google#2478, this cleans up the code blocks when all that is needed is a trivial debug print statement. Only making changes to Day 1 morning session so that I can get feedback before proceeding with the rest of the course. --------- Co-authored-by: Eric Githinji <[email protected]>

Part of google#2478 to clean up code blocks when all that is needed is a trivial debug print statement. In certain slides (8.1, 9.2, 9.3, 10.5) I've opted to retain the use of println! because dbg! makes it less readable. The dbg! macro uses pretty-printing by default and this results in a simple array such as the one in 8.1 being printed vertically instead of a cleaner one-liner. Co-authored-by: Eric Githinji <[email protected]>

Part of google#2478 to clean up code blocks when all that is needed is a trivial debug print statement. As in the other related PRs, in some places I opted to stick to println! for better readability.

Part of google#2478 to clean up code blocks when all that is needed is a trivial debug print statement. As mentioned in previous related PRs, in some places I've opted to retain the use of println! because dbg! makes it less readable.

Part of #2478 to clean up code blocks when all that is needed is a trivial debug print statement. As mentioned in previous related PRs, in some places I've opted to retain the use of println! because dbg! makes it less readable. Co-authored-by: Eric Githinji <[email protected]>

Part of google#2478 to clean up code blocks when all that is needed is a trivial debug print statement.

Part of #2478 to clean up code blocks when all that is needed is a trivial debug print statement. Co-authored-by: Eric Githinji <[email protected]>

Part of google#2478 to clean up code blocks when all that is needed is a trivial debug print statement. The deep dive sessions didn't have that many occurrences of trivial println! statements. I believe this can close google#2478.

mgeisler mentioned this issue Nov 28, 2024

Show stderr from code blocks #531

Closed

mgeisler mentioned this issue Dec 11, 2024

uk: avoid translating fixed strings in protobufs #2507

Closed

mgeisler added the good first issue Good for newcomers label Dec 11, 2024

Alx-Lai mentioned this issue Jan 14, 2025

Revert "Exercise: method and traits: change output" #2548

Merged

mgeisler pushed a commit that referenced this issue Jan 15, 2025

Revert "Exercise: method and traits: change output" (#2548)

aa548f4

Reverts #2383 Since #2397 is merged, to align the goal in #2478, rollback this temp workaround.

egithinji pushed a commit to egithinji/comprehensive-rust that referenced this issue Feb 21, 2025

Use dbg! instead of println! in Day 1 mng session.

372b587

Part of google#2478.

egithinji mentioned this issue Feb 21, 2025

Use dbg! instead of println! in Day 1 mng session #2652

Merged

djmitche linked a pull request Feb 21, 2025 that will close this issue

Use dbg! instead of println! in Day 1 mng session #2652

Merged

djmitche removed a link to a pull request Feb 21, 2025

Use dbg! instead of println! in Day 1 mng session #2652

Merged

djmitche mentioned this issue Feb 21, 2025

Preserve line numbers by not injecting a newline #2653

Merged

egithinji mentioned this issue Feb 22, 2025

Use dbg! instead of println! in Day 1 aft session #2654

Merged

egithinji mentioned this issue Feb 25, 2025

Use dbg! instead of println! in Day 2. #2657

Merged

egithinji pushed a commit to egithinji/comprehensive-rust that referenced this issue Feb 27, 2025

Use dbg! instead of println! in day 3 & 4.

96fc077

Part of google#2478 to clean up code blocks when all that is needed is a trivial debug print statement.

egithinji mentioned this issue Feb 27, 2025

Use dbg! instead of println! in day 3 & 4. #2669

Merged

djmitche pushed a commit that referenced this issue Feb 27, 2025

Use dbg! instead of println! in day 3 & 4. (#2669)

ea53e3c

Part of #2478 to clean up code blocks when all that is needed is a trivial debug print statement. Co-authored-by: Eric Githinji <[email protected]>

egithinji linked a pull request Feb 28, 2025 that will close this issue

Use dbg! instead of println! in deep dive sessions. #2676

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Use `dbg!` instead of `println!` for simple debug prints #2478

Use `dbg!` instead of `println!` for simple debug prints #2478

mgeisler commented Nov 28, 2024

egithinji commented Feb 17, 2025

Use dbg! instead of println! for simple debug prints #2478

Use dbg! instead of println! for simple debug prints #2478

Comments

mgeisler commented Nov 28, 2024

egithinji commented Feb 17, 2025

Use `dbg!` instead of `println!` for simple debug prints #2478

Use `dbg!` instead of `println!` for simple debug prints #2478