dodexahedron

Correct. Attributes are metadata only, and custom attributes do not/cannot affect program execution unless explicitly searched for and acted upon by the consuming code.

Only when absolutely necessary. Per the [property design guidelines](https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/property): >❌ AVOID throwing exceptions from property getters. > Property getters should be simple operations and should not have any preconditions. If...

In terms of dotnet design guidelines and formality/completeness of types, in relation to casts/type conversions: - If a lossy cast exists on a type, it should be `explicit` unless the...

If you prefer, that's fine with me. I only separated them as this one was meant more as a list of things that I think are important issues that deserve...

Haha nah. Just being verbose. I'd rather brain dump everything as it comes to me than forget about it. 😅 I figure the worst case is someone says "man, that...

No rush. I'll be better able to discuss it when I'm done with current work, as well.

Wait a second. Didn't I comment on this one yesterday? Or was that another issue very similar to this one? Or the other option: Did I not actually post what...

Ah yes... #3108 There's significant overlap. I'm going to copy all the text from both into a local file so I can go through and de-dupe, nuke items that are...

In any case, the interface thing is a better immediate piece of work for me to tackle, and will enable other work on those types to be a lot easier...

BTW: For adherence to the dotnet design guidelines for events, all EventArgs classes should end in "EventArgs" and should not be mixed use classes outside of events themselves (Key, for...