Array.Initialize should be marked with RequiresUnreferenceCode

[jkotas]

Array.Initialize calls value type default constructor via reflection. There is nothing preventing the value type default constructor from getting trimmed. See discussion in #77336 (comment)

However, adding RequiresUnreferencedCode on Array.Initialize has a ripple effect. It introduces warnings in situations where array type is passed into DynamicallyAccessedMembers(DynamicallyAccessedMemberTypes.All). We have some instances of this problem in our own libraries.

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to this area: @dotnet/area-system-runtime
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Array.Initialize calls value type default constructor via reflection. There is nothing preventing the value type default constructor from getting trimmed. See discussion in #77336 (comment)

However, adding RequiresUnreferencedCode on Array.Initialize has a ripple effect. It introduces warnings in situations where array type is passed into DynamicallyAccessedMembers(DynamicallyAccessedMemberTypes.All). We have some of these number of these in our own libraries.

Author:	jkotas
Assignees:	-
Labels:	area-System.Runtime
Milestone:	-

Tagging subscribers to 'linkable-framework': @eerhardt, @vitek-karas, @LakshanF, @sbomer, @joperezr
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Array.Initialize calls value type default constructor via reflection. There is nothing preventing the value type default constructor from getting trimmed. See discussion in #77336 (comment)

However, adding RequiresUnreferencedCode on Array.Initialize has a ripple effect. It introduces warnings in situations where array type is passed into DynamicallyAccessedMembers(DynamicallyAccessedMemberTypes.All). We have some of these number of these in our own libraries.

Author:	jkotas
Assignees:	-
Labels:	area-System.Runtime, linkable-framework
Milestone:	-

[tannergooding]

@jkotas what's the plan for this? Are we going to make the change (if so, ideally early in .NET 12) or should we just close this as not planned?

Is this something we rather need an updated analyzer or trimmer feature around first?

[jkotas]

@dotnet/illink Do you have an opinion what to do about this?

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @dotnet/illink
See info in area-owners.md if you want to be subscribed.