Nobuyuki Iwanaga

Would that problem be solved if it is recommended to use `ArgumentNullException.ThrowIfNull`? `ThrowIfNull` accepts the keyword e.g. `ArgumentNullException.ThrowIfNull(this)`.

What about `@args` in top-level statements?

I feel it seems a bit difficult to teach beginners the difference between private and intenal, because there are not so many opportunities for beginners to use IVT attributes.

Isn't the `private` keyword too casual to use for something that should not be taught?

Even now, people try to put private on top-level types mistaking it for internal. I think that if we introduce the private modifier, people will use private unintentionally and without...

These days, C# tends to make the most recommended style the easiest to write. If you want to encourage people to use `private` on top-level types and thus ignore IVTs,...

Does this work safely even if the code-cleanup automatically replaces spaces with tabs or vice versa?

It's on todo list. https://github.com/ufcpp/BitFields/blob/master/src/BitFieldsAnalyzer/BitFieldsAnalyzer/BitNAnalyzer.cs#L52 I think it's necessary but a bit hard task.

It's by design. I'd like to avoid overhead. Instead, I have a plan to another version of BitX implementation: - unchecked (current implementation): no runtime check, a public field, implicit...

I want: