Skip to content
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

CompatHelper: bump compat for "Optim" to "1.0" #302

Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 6, 2020

This pull request changes the compat entry for the Optim package from 0.20, 0.21, 0.22 to 0.20, 0.21, 0.22, 1.0.

This keeps the compat entries for earlier versions.

Note: I have not tested your package with this new compat entry. It is your responsibility to make sure that your package tests pass before you merge this pull request.

@antoine-levitt
Copy link
Member

Why the commit? I don't particularly mind, I'm just wondering how we should do this kind of things. Isn't it better to leave all the possibilities open to not cause conflicts in packages?

@mfherbst
Copy link
Member

mfherbst commented Sep 7, 2020

Main reason is cleanup. I don't think anyone working with DFTK master will still need to use the old Optim. Also gives the chance to use new features.

@mfherbst mfherbst merged commit b68fa68 into master Sep 7, 2020
@mfherbst mfherbst deleted the compathelper/new_version/2020-09-06-00-19-27-189-2438504951 branch September 7, 2020 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants