-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rethink type system: Mutable vs Immutable #32
Comments
If purpose is performance, then mutability is important. If purpose is functional style, then it is easier to work with immutable data. |
The idea is to be mutable by default, as most simple use cases do not use Im in the middle of the rewrite, but it is sometimes not easy to support both while having the some out-facing API. |
Currently the default type is described as "immutable" but in realty it's just a "copy-on-write" instance.
It would make more sense if the default instance is mutable, with wrapper to make it immutable.
The text was updated successfully, but these errors were encountered: