Gunnar Liljas
Gunnar Liljas
Indeed I did misunderstand/misread. Yes, that's a good question.
There's very little benefit to that, and a couple of downsides. I agree it should not be a struct though. It should be a class.
Yes, it would definitely warrant a new major version, but I still would strongly recommend that this change is made. No Money value would ever have a null currency, and...
> I personally am not wild about throwing an argument exception in the `Money` constructor. Replacing with a "null object" pattern would probably be better. That would help prevent from...
AFAIK, no RDBMS other than SQL Server can actually handle a DateTimeOffset with any credibility. Some, like Postgres, can certainly store it, but the value is converted to UTC and...
Yes, that change makes sense. Perhaps even on a broader scale, not only for DateTimeOffset.
If you can provide your own instances of the mapping classes, you can call the AddMapping which takes an IConformistHoldersProvider instance.
The inner join is expected and correct. That's how .Join is supposed to work. Edit: Ok, you're saying that the property joins should be left joins. Possibly so.
If the objective is to solve a problem in an existing code base, why not just change the string type used, to one where this modification has been applied? That...
Thanks for bringing this topic up. It's very interesting and there are certainly things that can be done better. IObjectsFactory vs IServiceProvider is not (yet) a point of importance to...