-
Notifications
You must be signed in to change notification settings - Fork 17
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
fstar-mode.el release matching F* release #47
Comments
That's a great idea! |
Did an fstar-mode.el release corresponding to F* v0.9.4.0 |
Is the release also tagged in MELPA in some way? |
No clue about Melpa. Maybe @cpitclaudel can help with that? |
Hi all, Thanks Catalin for pushing a tag. Tags are automatically picked up by MELPA stable (a variant of MELPA that doesn't track projects' master branch), which means that fstar-mode is now available to users of MELPA stable (I'm not sure it was before). There are not that many users of MELPA stable, though, so all of this isn't too important. More to the point: Emacs' package manager doesn't let you get anything but the latest version of a package; the usual approach is just to support all relevant versions in the same package. I added version detection to fstar-mode, so we should be able to handle any discrepancies between versions in there. Are there concrete problems in fstar-mode currently (that is, are there still-in-use versions of F* that it doesn't work with?) |
Barring minor bugs, fstar-mode is currently compatible with F* master and v0.9.4.0. |
Thanks. Pointers to these (I haven't been very good at keeping up lately) would be appreciated, so I can fix them :) |
This gets rid of the "non-empty prover response" warning, since it doesn't apply anymore. Fixes #47.
This gets rid of the "non-empty prover response" warning, since it doesn't apply anymore. Fixes #47.
I'm wondering whether it would be possible to tag an fstar-mode.el release corresponding to the new F* release we did yesterday, so that people who want to use the binary package have some chance to also use a working version of the interactive mode. This would increase the value of our releases and thus motivate us to release some more :)
The text was updated successfully, but these errors were encountered: