@@Vagelis_Prokopiou C# user here, still you are "required" to set the "required" keyword and if your team mates are not putting attention into the PR's this could mean bugs!
The main point is just that rust provides this out of the box and prevent on a code base of many maintainers to do less bugs because the language itself is not flexible enough to let you do that mistake otb for example one change dotnet c# did is to allow you to do strict non string nulls on the csproj
You're given a warning in your IDE that your strings aren't initialized in the default constructor (which is why you had the yellow underline). If you want, you can set this warning to be treated as an error by the compiler.
The next version of c# this November will have the required keyword, which, by using them, you can force of initialization of attributes.
FYI: C# 11 introduced the "required" keyword!
Hi Cosmin S. Yes, I know. Thanx.
@@Vagelis_Prokopiou C# user here, still you are "required" to set the "required" keyword and if your team mates are not putting attention into the PR's this could mean bugs!
The main point is just that rust provides this out of the box and prevent on a code base of many maintainers to do less bugs because the language itself is not flexible enough to let you do that mistake otb for example one change dotnet c# did is to allow you to do strict non string nulls on the csproj
@@jonatthu Right on the money 🙂
@@jonatthu Right on the money #2 🙂
You're given a warning in your IDE that your strings aren't initialized in the default constructor (which is why you had the yellow underline). If you want, you can set this warning to be treated as an error by the compiler.
Thanks for the tip Marshall.