ordering in map.zipmap #2
Description
based on PFA spec 0.8.1, map.zipmap should be order-agnostic (unlike a.zipmap). However, it appears that both titus2 require the maps in the parameter to have the same order of keys. Ordering of keys are not easily preserved. A simple map.map could shuffle key order. No straight forward workaround is available, as there is no native sorting function in the map manipulation library.