-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add MMaps to Coq Platform #307
Comments
Justification of usage here is associated to the efficiency gain when migrating. I would suggest that this should be better advertised on the MMaps main page. Also, the MMaps main page contains a caveat about unstable interfaces that might deter potential users from migrating. Is this caveat pragmatically important? |
@ybertot there are in my view two main arguments for people to migrate from
The caveat about interface stability is to my knowledge a remnant from when the library was under heavy development by Pierre. I would say the core interface is stable (and we can change the README to reflect this), but there could be additional utility results added over time, such as what Andrew did here. |
I agree, I only suggest you should remove the remnant. |
OK, I will address this in the next few days. |
For the record, the README issue was addressed in coq-community/mmaps#15 |
The inclusion of this contribution has been approved by the editorial board. |
MMaps is a library that contains several implementations of finite maps over arbitrary ordered types using Coq functors. This is an updated version of Coq Stdlib's FMaps. It is meant to complement the MSet library in Stdlib. One noteworthy advantage over the legacy FMaps is that MMaps has a fast red-black tree based finite map.
MMaps is currently maintained in Coq-community by myself and @letouzey and just had its 1.0 release. I propose that MMaps is added to the Coq Platform, so as to let FMap users migrate to it.
The text was updated successfully, but these errors were encountered: