I find it a little brittle that we do this specifically for synthesized void methods. Basically, whenever a new synthesized void method is added to the compiler/language, we could forget to change this. Would it be possible to remove the condition, identify the problematic void methods that we don't want to analyze, and then introduce a new condition which excludes those methods more specifically? That way when a new kind of synthesized void method comes about it will just be analyzed by default and the author will have to make a special effort to opt out of it.

I'd like to keep this change simple if possible in case we want to port this change to other branches. I've logged #58012 to update the condition separately.

(!method.IsParameterlessConstructor() || method.IsDefaultValueTypeConstructor(requireZeroInit: true))

It looks like this condition will be false for a synthesized parameter-less constructor of a class. Therefore, we are going to Analyze it, which we didn't do before. I assume that was not the intent of the change. #Closed

Good catch, thanks. I've updated the if condition.

I'm open to suggestions on how to improve the readability of the if though. It feels like the call to IsDefaultValueTypeConstructor(bool requireZeroInit) is the complicated part. One possibility is to change that method to return a value that describes the constructor (such as the enum below), but that might mean performing extra work for callers that don't care about requireZeroInit.

enum ValueTypeConstructorKind
{
    None,
    Explicit,
    ImplicitZeroInit,
    ImplicitWithFieldInitializers,
}