You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/fundamentals/code-analysis/quality-rules/ca1852.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ A type that's not accessible outside its assembly and has no subtypes within its
29
29
30
30
## Rule description
31
31
32
-
When a type isn't accessible outside its assembly and has no subtypes within its containing assembly, it can be safely sealed. Sealing types can improve performance.
32
+
When a type isn't accessible outside its assembly and has no subtypes within its containing assembly, it can be safely sealed. Sealing types can improve performance. For more information, see [Analyzer Proposal: Seal internal/private types](https://github.com/dotnet/runtime/issues/49944)].
33
33
34
34
If you apply <xref:System.Runtime.CompilerServices.InternalsVisibleToAttribute?displayProperty=fullName> to the assembly that's being analyzed, this rule doesn't flag types that aren't marked as `sealed` by default, because a field may be used by a friend assembly. To analyze the assembly anyway, see [Configure code to analyze](#configure-code-to-analyze).
0 commit comments