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

chore: Replace references to internal libraries with sublibraries #9576

Closed
wants to merge 1 commit into from

Conversation

414owen
Copy link

@414owen 414owen commented Dec 31, 2023

There seemed to be three terms for the same thing:

  • internal library
  • sublibrary
  • sub-library

These libraries aren't necessarily internal, as their visibility can be set to public.
My own use case for these libraries is to provide instances for typeclasses which require adding a dependency (so they're public facing).
I think we should settle on the term sublibrary, (or sub-library, if people feel strongly that we should appease spell-check).

Initially I was just going to change this in the docs, but I was using sed anyway, so in for a penny, in for a pound.

@geekosaur
Copy link
Collaborator

Have you looked at #9371?

Sublibraries can be internal, or not, as is the
case when `visibility` is set to `public`.
This commit changes the documentation to the
sublibrary nomenclature, as well as code comments,
error strings, etc.

I've also replaces the hyphenated sub-librar{y,ies}
spelling with sublibrar{y,ies}, which seemed more
popular anyway.
@414owen
Copy link
Author

414owen commented Dec 31, 2023

Ah, no, must have missed that.

Now that I look closely at the docs in my changeset, the changes don't make much sense.

@414owen 414owen closed this Dec 31, 2023
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