I’m late to the party, but this might still help someone… There’s actually a simple solution (but please read the warning below before using it). Define a base record type like this: public abstract record RecordWithValidation { protected RecordWithValidation() { Validate(); } protected virtual void Validate() { } } And make your actual record inherit … Read more
Per the C#9 record proposal, the following should compile, even if not very useful without actual implementations.. // No explicit IEquatable<R> – this is synthesized! public sealed record SimpleVo { // Not virtual, as SimpleVo (R) is sealed. // Accepts SimpleVo? (R?), and not SimpleVo (R), as argument. public bool Equals(SimpleVo? other) => throw new … Read more
It looks like there is currently no such type available. You can implement this yourself, but beware of the implications if you need this in a production-ready way. It’s not so simple as it may seem at first sight, as this answer by @ryanholden8 demonstrates! For my use case (and as a simplified example) I … Read more
Source Generators must be .NET Standard 2.0 to run in Visual Studio 2019+ or .NET Standard 1.x to run in Visual Studio 2017+.
But what about cloning? var r4 = r with { }; performs a shallow clone on r. The clone method is public according to the specification above. But what is its name? The C# compiler has a fairly common trick where it gives generated members names which are illegal in C#, but legal in IL, … Read more
This is a bug in the current preview and the latest master branch (June 27). A simple record in sharplab.io creates the same error. Just add the missing type somewhere in your project using System.ComponentModel; namespace System.Runtime.CompilerServices { [EditorBrowsable(EditorBrowsableState.Never)] internal class IsExternalInit{} } Records and init will work without problem. Only LinqPad 6 seems to … Read more
Short version Can your data type be a value type? Go with struct. No? Does your type describe a value-like, preferably immutable state? Go with record. Use class otherwise. So… Yes, use records for your DTOs if it is one way flow. Yes, immutable request bindings are an ideal user case for a record Yes, … Read more