Bent Rasmussen

Subtly different behavior depending on choice of open statement sounds like an accident waiting to happen. On the other hand I can't see a way to reconcile maximum conciseness with...

Maybe, it just sounded like watermark was the correct adorner because it can hide the text when the user enters text into the textbox - but I will take a...

Having analyzers for a trap like this would be great. One mitigation we are trying is to annotate all (many) structs with `[]` as well as a custom `IEquatable` implementation...

@En3Tho The only reason for adding `[]` was to get compiler errors so as to know what code to fix to use '==', as there is no compiler, analyzer or...

I found it hard to work with this feature turned on all the time, so I used this simple workaround: conditional compilation directives to distinguish between development builds and production...

A different example of this issue appears to be in Microsoft Coyote (actor library written in C#). There the base class Actor contains a protected attribute to be used by...

Interesting. In that case the C# folks should make an analyzer for it, since it breaks C#/F# interop. It is also interesting that this alleged bug has been used consciously...