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.

Sign up for GitHub

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

Jump to bottom

Versioning policy for Internal modules #8

Open
maoe opened this issue Dec 3, 2016 · 1 comment
Open

Versioning policy for Internal modules #8

maoe opened this issue Dec 3, 2016 · 1 comment
Labels
enhancement Specification

Comments

@maoe
Copy link
Member

maoe commented Dec 3, 2016

It's been a common practice in the Haskell community to put internal functions to Internal modules, which are not meant for a public API but for a semi-private API that can be useful to access library internals to extend the API. I think it's natural to relax the versioning policy for changes in those Internal modules. Should we mention it somehow in the PVP?
@hvr
Copy link
Member

hvr commented Dec 4, 2016 •
edited
Loading

Yeah, I think it makes sense to formalise this, as I'd like PVP-validation tooling to be able to be aware of that kind of convention

bgamari added a commit to bgamari/pvp that referenced this issue Nov 28, 2022
@bgamari
Formalize ".Internal" module convention
e4ad28f 
Here we formalize the convention of using `.Internal` modules
to provide potentially unstable interfaces.

Addresses haskell#8.
@bgamari bgamari mentioned this issue Nov 28, 2022
Closed
@bgamari bgamari mentioned this issue Mar 17, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Specification
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@maoe @hvr