LDM Notes for May 8th, 2024

[333fred]

https://github.com/dotnet/csharplang/blob/main/meetings/2024/LDM-2024-05-08.md

Agenda

• readonly for primary constructor parameters

[alrz]

Is changing the default also an option here? Currently records are intentionally opinionated and for anything outside the default you'd need to write your own class. I think this can apply to primary constructors, if you want mutable fields, you could declare mutable fields.

class C(int readonlyByDefault) {
  private int mutable = readonlyByDefault; // plus, capturing readonlyByDefault in this case is already a warning
}

[CyrusNajmabadi]

Yes. That's something we are interested in investigating. Part of a larger push around immutability.

[KennethHoff]

Option for Immutability by default; you heard it here first!

[HaloFour]

Yes. That's something we are interested in investigating. Part of a larger push around immutability.

Hmmm, your ideas are intriguing to me and I wish to subscribe to your newsletter.

[CyrusNajmabadi]

[TahirAhmadov]

In my code base, 100% (not exaggerating) of primary ctor parameters are "readonly" by actual usage. Personally, I fully support the default readonly approach.

[qrli]

I don't like the Analyzer solution. If that direction turned out to be the best choice, I'd at least like to have compiler warnings for assignments to primary constructor parameters.

PS: Thanks for your effort to push this forward.

[CyrusNajmabadi]

Analyzers can produce compiler warnings.