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

Drop support for 4.01 #272

Closed
aantron opened this issue Sep 22, 2016 · 2 comments
Closed

Drop support for 4.01 #272

aantron opened this issue Sep 22, 2016 · 2 comments
Labels
Milestone

Comments

@aantron
Copy link
Collaborator

aantron commented Sep 22, 2016

The main reason is to be able to use [@@ocaml.deprecated] to communicate API changes before/after some future major release. There are several other breaking changes that would benefit from this.

It's also a prerequisite for eventually removing the Camlp4 extension.

Please voice any objections.

@aantron aantron modified the milestone: 2.6.0 Oct 2, 2016
@rgrinberg
Copy link
Contributor

0 objections from me.

But Is there a way to check out which opam packages still use the obsolete camlp4 extension? Would be better to still warn people about this. Since the camlp4 removal itself will be without a deprecation cycle

@aantron
Copy link
Collaborator Author

aantron commented Oct 19, 2016

I have a script on my machine that downloads all transitive dependents of Lwt found in OPAM, which I then look through (usually grep) for things like this. So, yes, I will warn at least the maintainers of those packages.

I will also mark lwt.syntax and the Camlp4 module as deprecated for a while, though I don't think I can get an automatic warning for this like for "normal" Lwt code. Haven't tried it yet.

@aantron aantron modified the milestone: 2.7.0 Nov 19, 2016
aantron added a commit that referenced this issue Nov 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants