Primary constructors, the new C# 12 feature, have caused some concerns for developers when using it with dependency injection.

DiscDot provides insights into distributed systems, cloud computing, and scalable architectures, offering articles and best practices for designing and implementing resilient and scalable distributed systems. By exploring DiscDot's curated content, developers can learn about distributed data storage, fault-tolerance mechanisms, and distributed computing frameworks for building highly available and performant applications. Whether you're architecting microservices, deploying containerized workloads, or managing distributed databases, DiscDot offers  insights and practical guidance to help you tackle the challenges of building distributed systems.

Discover .NET

Concerns have been raised by C# developers regarding the use of primary constructors for dependency injection. While primary constructors reduce code bloat, the mutability of parameters can lead to instances being changed in other parts of the class, increasing the risk of runtime exceptions. There are discussions about adding read-only parameters to primary constructors in the future.

Primary constructors has caused concerns for C# developers

Why is it a problem to lose the read-only part?

<p>I love using them on classes that are created via dependency injection so the mutability is far less concerning for me. It would be very out of place to be assigning null to them.</p>
<p>BUT I’d love if I could make them read-only too!</p>
