Skip to content

Commit 401bace

Browse files
authored
Add proposal link with additional info on why sealing types improve performance (#42505)
1 parent 18299b4 commit 401bace

File tree

1 file changed

+1
-1
lines changed
  • docs/fundamentals/code-analysis/quality-rules

1 file changed

+1
-1
lines changed

docs/fundamentals/code-analysis/quality-rules/ca1852.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ A type that's not accessible outside its assembly and has no subtypes within its
2929

3030
## Rule description
3131

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)].
3333

3434
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).
3535

0 commit comments

Comments
 (0)