Why do I NOT get warnings about uninitialized readonly fields?

Question

The C# compiler is kind enough to give you a \"field is never assigned to\" warning if you forget to initialize a readonly member which is private or internal, or if the cla

Answer 1

This is MSDN Documentation: Compiler Warning (level 4) CS0649:

Field 'field' is never assigned to, and will always have its default value 'value'

The compiler detected an uninitialized private or internal field declaration that is never assigned a value.

So, for non-internal and non-private fields you shouldn't expect to have a warning.

But I think the main reason is that C# compiler believes that you should initialize all the things that are accessible just from your assembly. I guess C# compiler left it to the others to initialize non-private and non internal fields in their assembly.

But I tested protected internal and I don't know why C# compiler doesn't warn about it.