Brandon Bonds

Government approval processes often become roadblocks and cause systems and data to become stale and unreliable for their purposes. I fear the same for this effort. As red tape is...

My thoughts: 1. Requires agencies to release source code and documentation corresponding to any release build (build deployed for production use). 2. Releasing source code for non-release builds is acceptable...

Pros/cons for 2 vs 3? Both are DRY but I prefer 2... you don't buy much visually with 3.

I support 1 even with the inclusion of 2 or 3. It helps to document the parameters.

I would prefer assembly. It is a common style to organize one-class-per-file, and limiting the scope of inheriting a `closed` type to the same file would break that style.

`assembly` is even a keyword.

https://github.com/dotnet/roslyn/blob/23ddb23da69d7a7af78403ae27039ccc1660c97e/src/Compilers/CSharp/Portable/Syntax/SyntaxKind.cs#L166

`this.` can be used to access class members which are hidden by locals. Presumably it would also be used for property-scoped field access. But if name collisions were allowed, then...

@lachbaer Why not just use a nested type? Nested types exist (in part) to provide a lot of additional encapsulation, and they do so with additional overhead. There is performance...

To clarify, I not only believe that "property-scoped everything" is a separate proposal from this, but that your specific suggestion of adding `: struct` and `: class` is a separate...