[Utility][Container] Support non-nullable types in Array::Map #17094
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this commit, the
Array::Mapmember function could only be applied to nullable object types. This was due to the internal use ofU()as the default value for initializing the outputArrayNode, whereUis the return type of the mapping function. This default constructor is only available for nullable types, and would result in a compile-time failure for non-nullable types.This commit replaces
U()withObjectRef()inArray::Map, removing this limitation. Since all items in the output array are overwritten before returning to the calling scope, initializing the output array withObjectRef()does not violate type safety.