CDocumentation says that non-nullable reference types “must be initialized to a non-null value” and “compiler issues a warning when code assigns maybe-null”
CYet in the picture which is from a dotnet entity framework video, they just set firstname and lastname, non-nullable reference types, to null
CHow? It says you can’t initialize to null value
T essentially forces the compiler to shut up about nullability warning.
TYou can set non-nullable reference types to null just fine, it's just the compiler which will warn you about it.
TBut if you say "shut up" to the compiler then it won't complain
CThank you. I dont see why you would want to lose the warnings? If you don’t want the warnings and can still set it to null, why not use a nullable reference type?
CSo the “?” only affects compiler warnings and doesn’t affect the behavior of the variable?
TFor reference types, yes
TSometimes you have a situation (like with EF) where you don't have an initial value to set anything to, but you know for certain that the value won't be null when you actually access it.
TEF will set those values for you before you can properly access them
CAnswered before I could ask, are you saying it has a default constructor? If you don’t initialize firstname for example, will it just make it white space?
TStrings are by default null
TAll reference types are by default null
CBut you said “EF will set those values for you before you can properly access them”. I’m talking in that scenario.
TI mean that when you access a model, EF with have initialized it already