If we use a discarding diagnostic bag (`!AccumulatesDiagnostics`), the `MergeAndClear` method asserts. We should consider addressing this during MQ. Follow-up on https://github.com/dotnet/roslyn/pull/72948#discussion_r1571141985, since we worked around with: ``` internal void LookupImplicitExtensionMembersInSingleBinder(LookupResult result, TypeSymbol type, string name, int arity, ConsList<TypeSymbol>? basesBeingResolved, LookupOptions options, Binder originalBinder, ref CompoundUseSiteInfo<AssemblySymbol> useSiteInfo) { ... if (tempUseSiteInfo.AccumulatesDiagnostics) { useSiteInfo.MergeAndClear(ref tempUseSiteInfo); } ```