@malwareminigun Oh good it wasn’t just me.

@bradwilson Any change will cause us to re-run the CompilationStartAction callback. And since I didn't quite make it clear; you can use the context given in the compilation start action to register further things. For example: https://github.com/dotnet/roslyn-analyzers/blob/d6e7d82e631f0b4c2519284a1c12ed9eb945a388/src/NetAnalyzers/Core/Microsoft.NetCore.Analyzers/Tasks/UseValueTasksCorrectly.cs#L93 See how this is checking for some types to exist, and only if it does, it registers something further against the compilation context.

@bradwilson That way you'll do the top-level checks first, and you can register the additional checks after they pass. And to get the assembly-level attributes, compilation.Assembly.GetAttributes()

@bradwilson Have your analyzer register a CompliationStartAction, which gives you the compilation. You can get the attributes for the compilation to check for what you need. Then inside that action, register the Symbol/SyntaxNode actions as needed.

@KirillOsenkov In your defense, it took them a few months.