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

Discussion: splitting Cabal and Cabal-syntax into public and private APIs #10294

Open
geekosaur opened this issue Aug 30, 2024 · 0 comments
Open
Labels
re: API Concerning the Cabal API design type: discussion

Comments

@geekosaur
Copy link
Collaborator

#10259 revealed that Cabal and to a lesser extent Cabal-syntax have very large APIs which are currently completely "public". It would be good to determine which APIs are actually public and move the rest into private libraries. There is some discussion in that issue, but sorting out the API is necessarily going to be a long term effort.

  • example 1: compat modules (e.g., shall we encourage tool writers to use base-compat from Hackage instead of our ancient hacks?)
  • example 2: cabal-solver API (here the problem was, it seems, enshrining that this is internal, so it suddenly became external; also there seems to be an active user)
@geekosaur geekosaur added type: discussion re: API Concerning the Cabal API design labels Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
re: API Concerning the Cabal API design type: discussion
Projects
None yet
Development

No branches or pull requests

1 participant