Question: How does this compare to seamless-immutable? about icepick

[aearly]

These two are very similar in their goals, but differ in the API. seamless-immutable overloads certain array methods, such as [].map and [].filter to return immutable values, but I leave the built-ins alone and instead provide icepick.map(arr, fn), icepick.filter(arr, fn), etc. functions (similar to how lodash/underscore do it). This is to make interop with other libraries easier -- other libraries might rely on the array built-ins returning mutable collections.

Overall the API is more like mori than a fluent/method-based API.

icepick doesn't support freezing Dates currently -- it will leave them as-is, unfrozen. I'm considering converting them to timestamps or ISO date strings. It also will throw if it is used with a collection with circular references -- doing that prevents some nasty bugs.

[holyjak]

Thanks a lot! Perhaps it would be useful to add this to the README?