Jason Bock

I concur with @rockfordlhotka. If a parameter is a NRT, someone could still pass in `null`, so an `ArgumentNullException.ThrowIfNull()` call is warranted.

@rockfordlhotka don't make me do it.... 

If a property can be `null`, it needs to be annotated as such. And yes, that means that **every** usage of that property needs to do a null check. If...

The current behavior states that `null` is a valid value, so it should be annotated with `?`. However, I'm guessing this will be part of a breaking change release, so...

I would not be against this. I wrote a `WriteLines()` extension so I can do raw string literals with `IndentedTextWriter` when I can, but I'm sure I've missed some areas,...

@MitchRazga I'll assign this to the 10.1.0 milestone. I don't think we'll have time to get this in with 10.0, but I'm interested in seeing what this can do, especially...

@MitchRazga Thanks for the kind comments about Rocks. While it's not my intention to have everyone move from another mocking library (like NSubstitute), it's nice to hear someone think that...

> It makes sense that any input into the `out` parameter gets overridden with `Arg.Any()`. I mainly only mentioned this because the `ThrowIfNull` still gets generated, meaning you can't input...

I think if this is done, we should merge [this issue](https://github.com/JasonBock/Rocks/issues/268) in with this, because this will inevitably get in the way of this work (probably), so, probably want to...

Huh, that's an interesting one. Glad that you have a workaround 🙂. I'm busy this weekend, but I'll take a look at it when I get back. Thanks for reporting...