Skip to content

Fix build warnings #12134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gewarren merged 1 commit into from
Dec 11, 2025
Merged

Fix build warnings #12134

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions xml/System.Runtime.InteropServices/TypeMapAssociationAttribute`1.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@

## Remarks

Types used in a managed-to-unmanaged interop operation can use <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute%60%601> to define a conditional link between the source and proxy type. If the source is kept, so is the proxy type. If trimming observes an explicit allocation of the source type, the entry is inserted into the map.
Types used in a managed-to-unmanaged interop operation can use <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute`1> to define a conditional link between the source and proxy type. If the source is kept, so is the proxy type. If trimming observes an explicit allocation of the source type, the entry is inserted into the map.

When an application is trimmed, an entry in the Proxy Type Map is included when the "source type" is referenced in one of the following ways in reachable code:

Expand All @@ -62,7 +62,7 @@ Finally, if the trimming tool determines that it's impossible to retrieve a <xre
> Conflicting key/value mappings are not allowed.

> [!NOTE]
> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it isn't guaranteed that the <xref:System.Runtime.InteropServices.TypeMapAttribute%60%601>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute%60%601>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTarget%60%601> attributes are present in the final image after a trimming tool has been run.
> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it isn't guaranteed that the <xref:System.Runtime.InteropServices.TypeMapAttribute`1>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute`1>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTargetAttribute`1> attributes are present in the final image after a trimming tool has been run.

]]></format>
</remarks>
Expand Down
4 changes: 2 additions & 2 deletions xml/System.Runtime.InteropServices/TypeMapAttribute`1.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@

## Remarks

Types involved in unmanaged-to-managed interop operations can be referenced in a <xref:System.Runtime.InteropServices.TypeMapAttribute%60%601> assembly attribute that declares the external type system name, a target type, and optionally a "trim target" to determine if the target type should be included in the map. If the constructor that doesn't take a trim target is used, the entry is always emitted into the type map.
Types involved in unmanaged-to-managed interop operations can be referenced in a <xref:System.Runtime.InteropServices.TypeMapAttribute`1> assembly attribute that declares the external type system name, a target type, and optionally a "trim target" to determine if the target type should be included in the map. If the constructor that doesn't take a trim target is used, the entry is always emitted into the type map.

When an application is trimmed, an entry in the External Type Map is included when the "trim target" type is referenced in one of the following ways in reachable code:

Expand All @@ -65,7 +65,7 @@ Many of these instructions can be passed a generic parameter. In that case, the
> Conflicting key/value mappings are not allowed.

> [!NOTE]
> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it isn't guaranteed that the <xref:System.Runtime.InteropServices.TypeMapAttribute%60%601>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute%60%601>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTarget%60%601> attributes are present in the final image after a trimming tool has been run.
> The underlying format of the produced maps is implementation-defined. Different .NET form factors might use different formats. Additionally, it isn't guaranteed that the <xref:System.Runtime.InteropServices.TypeMapAttribute`1>, <xref:System.Runtime.InteropServices.TypeMapAssociationAttribute`1>, and <xref:System.Runtime.InteropServices.TypeMapAssemblyTargetAttribute`1> attributes are present in the final image after a trimming tool has been run.

]]></format>
</remarks>
Expand Down