Joseph Musser

Yep, https://www.ecma-international.org/publications/files/ECMA-ST/ECMA-335.pdf, section **II.23.3 Custom attributes**, page 268: > - If the parameter kind is _System.Type_, (also, the middle line in above diagram) its value is stored as a _SerString_...

@ymassad TypeDescriptor will inject the type as a constructor parameter when it instantiates a type converter specified via TypeConverterAttribute, and maybe you can follow a similar pattern in the meantime?...

> @ymassad The problem there (if I remember the metadata format correctly) is that attribute arguments of type System.Type are stored as serialized strings containing the assembly-qualified name. What string...

@HaloFour > My opinion is that this proposal makes auto-implemented properties more difficult to read by introducing these silent backing fields despite the use of logic. I don't disagree with...

I think a `field` property modifier is unnecessary verbosity. The keyword should just be available for use the same place you look at to see the backing field anyway.

@lachbaer That is going to be such a rare scenario, it's a shame it has to make the common case worse for everyone.

@DavidArno > Technically, I could do that. But I'd prefer to gouge my own eyes out to be honest. This confuses me. It's like another kind of namespace. More logical...

@DavidArno How does nesting implementations within an abstract class cause the abstract class to have more than one responsibility? The fact that types are declared inside it doesn't make the...

It gets weirder. Not sure what to make of this. Looks like tuples in the `select` clause get all elements forced to be typed as non-nullable too:  Non-tuples, too:...

More weirdness.