Dominique Schuppli

> to expect a new person to come here wanting to know how to use a library to be the one to document it seems a bit ridiculous to me...

I can actually confirm this myself: This is most likely due to a Roslyn bug; see https://github.com/dotnet/roslyn/issues/4434. I think it might be helpful to leave this present issue open to...

@dotnetjunkie, just FYI, your template assumes that assembly versions are steadily increasing for each new release of a project. This may be the case for most "well-behaved" projects, but there...

@riezebosch: Looking good. Btw., if you subclass `LookupOrFallbackDefaultValueProvider` instead of `DefaultValueProvider`, you'll get automatic support for default values wrapped in completed `Task` and `ValueTask`. In case you want that.

@zvirja: Thanks for the reminder! Someone noticed a while ago over at Moq's repo that due to the accessibility of `DefaultValueProvider`'s methods, these providers aren't as composable as they could...

> ref/out parameters, moq doesn't seem to visit the value provider for that As far as I can tell, from Moq's perspective, that's by design: * `ref` parameters are assumed...

@riezebosch: > Minor correction, for the ref parameter the value provider is visited but for some reason the variable doesn't get overwritten (probably boxing or something like that?). Strange... none...

> It's in my reply above: #1139 (comment) I ran those tests, which fail (as expected). > Minor correction, for the ref parameter the value provider is visited I tried...

@riezebosch, I cannot reproduce your `RefParameter` test result using Moq 4.13.0, the above code, and the two interfaces as defined below. Both tests fail due to the default value provider...

We have been discussing possible futures / alternatives for sequences in #75 (and perhaps a few other issues that I don't remember right now). That issue has been around for...