Maps using values' monoidal structure during merging
Go to file
2019-08-24 06:19:03 -04:00
src/Data Make functions correspond more closely to Data.Map behavior 2019-08-22 09:11:28 -04:00
.gitignore ignore cabal newstyle outputs. 2018-08-30 12:58:33 -04:00
.travis.yml ci: Build split-these set to false as well 2019-08-05 00:09:00 -04:00
Changelog.md Make functions correspond more closely to Data.Map behavior 2019-08-22 09:11:28 -04:00
default.nix default.nix: Update for 0.6 2019-08-24 06:19:03 -04:00
LICENSE Monoidal map 2015-01-20 11:12:30 -05:00
monoidal-containers.cabal Make functions correspond more closely to Data.Map behavior 2019-08-22 09:11:28 -04:00
README.md Create README.md 2015-02-12 17:26:22 -05:00
Setup.hs Monoidal map 2015-01-20 11:12:30 -05:00

monoidal-containers

Often when working with the containers offered by the containers and unordered-containers packages one would prefer the monoidal structure of the values to be used when resolving conflicts between keys when merging structures. Sadly, these are not the semantics offered by the provided instances. This package provides newtypes with an appropriate set of instances and utility functions to make them usable.