Add an alias for the primary constructor

[Mr0N]

I liked the primary constructor more or less, but there is a problem that the external API depends on the internal implementation. That is, if you change the name of the constructor parameters, the entire logic of the program will break. I suggest adding aliases for the constructor parameters.

 public class MoveGeoResult(Config config alias _config, Node node alias _node) : IMoveGeoResult
 {
     public void MoveGeo()
     {
      
     }

 }

[HaloFour]

if you change the name of the constructor parameters, the entire logic of the program will break.

How does that make it different from any other identifier in C#?

[HaloFour]

Not so many people look at compiler warnings.

That sounds like their problem. The warning can be promoted to an error if someone wants to ensure that it breaks compilation.

[Mr0N]

well, I don't know, it's easier to add aliases, there will be fewer problems, and the constructor will not violate encapsulation

[HaloFour]

it's easier to add aliases

Adding language features is not easy.

and the constructor will not violate encapsulation

There is no violation of encapsulation. To the outside world the parameter names are the only thing that matters. Consumers aren't even aware that primary constructors exist. How the parameters are used within the type are entirely implementation details.

[Mr0N]

https://github.com/dotnet/runtime/blob/main/src/libraries/System.Collections/src/System/Collections/BitArray.cs
For large classes, the primary constructor turns into a disaster

[HaloFour]

Primary constructors aren't intended to be used with all classes, nor are they intended to replace normal constructor syntax. They are an opinionated short-hand for simple scenarios. BitArray is definitely not one of those scenarios.

[Mr0N]

That is, the main name is displayed for the main user, and aliases are available only for the implementation of the class