Wildcard maps do not propagate their key/value types properly when assigned a map type. I was attempting to make a “Create map from Arrays” macro, as an example. If you assign a map variable to a wildcard map pin, in a macro like below, then it changes the “Value” pin to the type of the key, instead of the type of value, as shown below:
On a related note - it would be nice to have “Local Map of Wildcards” and “Local Set of Wildcards/ints” etc (like there are for arrays), that would make macros like this tidier to use (wouldn’t have to pass a map variable in by reference for modifying, can just output the created map). That said, I wouldn’t want to be the one coding anything to do with wildcards… seems like a nightmare of edge cases.
Thank you for submitting a bug report. I have reproduced this issue and logged a report for it here
You can track the report’s status as the issue is reviewed by our development staff. Please be aware that this issue may not be prioritized or fixed soon.
Any new issues on this topic or reasons, why this is backlogged? Still stumbling over the same limitation in 4.23 while trying to create simple map iteration macros…
This actually has relevancy. If you’re working with maps a lot, you can avoid a LOT of duplicate logic with simple wildcard macros. Unfortunately, the type is incorrect.
