[Chapel Merge] Retire old map future and add new future to replac

Branch: refs/heads/main
Revision: ea6b72c
Author: bmcdonald3
Link: Retire old map future and add new future to replace it by bmcdonald3 · Pull Request #18633 · chapel-lang/chapel · GitHub
Log Message:

Merge pull request #18633 from bmcdonald3/map-future

Retire old map future and add new future to replace it

[ reviewed by @daviditen ]

PR #18523 added a new in the initializer for the chpl__hashtable in map, which caused this future test that was failing due to #15929 to be resolved, even though the underlying issue wasn't fixed, which is a known issue with default initializing a record with type that isn’t known until runtime. I spoke with David and decided to retire the old future and add a new one to keep tracking the underlying issue. The setOfArray future is unrelated and is failing due to #16033, a compiler issue.

Modified Files:
A test/types/chplhashtable/new-hashtable.chpl

A test/types/chplhashtable/new-hashtable.future
A test/types/chplhashtable/new-hashtable.good
R test/library/standard/Map/mapOfArray.future
R test/library/standard/Map/mapOfArray.skipif
M test/library/standard/Map/mapOfArray.chpl
M test/library/standard/Map/mapOfArray.good

Compare: https://github.com/chapel-lang/chapel/compare/883563e3efc0...ea6b72c1c3f2