testing: add explanatory commentary to solution#3062
Conversation
This commentary, written by Gemini, focuses on aspects of the solution that differ from the baseline languages (C/Java/Python), highlighting Rust-specific idioms and concepts.
src/testing/solution.md
Outdated
| - Note that `c.to_digit(10)` returns `Some(digit)` if `c` is a base-10 digit, | ||
| and `None` otherwise. | ||
| - The condition `digits >= 2 && sum % 10 == 0` ensures both requirements are | ||
| met. |
There was a problem hiding this comment.
What's the principle behind moving these specific items into speaker notes?
There was a problem hiding this comment.
The same question applies to all other PRs, including those that I merged. Could you take another look?
There was a problem hiding this comment.
Looking at this example, I interpret the difference to be that the Gemini saw this API detail about to_digit as not important enough to put into the main text.
The non-speaker note text is firmly about the solution: what was made. The background information about to_digit is, well, more background.
I can make a pass and have it take out non-essential stuff like this.
There was a problem hiding this comment.
Alright, I asked Gemini what it had to say for itself 😄 It came back with
- Main Text: Concise summary of the logical fixes required by the exercise.
- Speaker Notes: Deep-dive into Rust-specific design (Unicode, Option ergonomics, and architectural choices) that provide value for experienced engineers without needing comparison to other ecosystems.
I had it update the text based on this, let me know what you think!
dbb6993 to
1b1ae62
Compare
- Remove redundant or overly simplistic explanations. - Focus on Rust-specific idioms and design choices. - Clean up formatting and technical depth.
1b1ae62 to
1d5ba26
Compare
This commentary, written by Gemini, focuses on aspects of the solution that differ from the baseline languages (C/Java/Python), highlighting Rust-specific idioms and concepts.