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

Dependency upper bounds #371

Closed
ocramz opened this issue Dec 31, 2023 · 1 comment
Closed

Dependency upper bounds #371

ocramz opened this issue Dec 31, 2023 · 1 comment
Labels
easy fix feedback needed Please Read!
Milestone
Release 0.22

Comments

@ocramz
Copy link
Collaborator

ocramz commented Dec 31, 2023 •
edited
Loading

  1. WHY
  2. They are such a waste of time. E.g. in the past couple months alone I had to patch scotty to accept higher versions of bytestring and text.
  3. Nothing, neither PVP, nor SemVer, nor any amount of similar hand-written metadata, indicates that a dependency changing version will break any downstream library. This can only be observed experimentally.
  4. Shall we just get rid of the ones that don't explicitly break the interface?
@ocramz
Copy link
Collaborator Author

ocramz commented Mar 9, 2024

closed (for now) by #377

@ocramz ocramz closed this as completed Mar 9, 2024
@ocramz ocramz added this to the Release 0.22 milestone Mar 9, 2024
@ocramz ocramz mentioned this issue Mar 10, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
easy fix feedback needed Please Read!
Projects
None yet
Milestone
Release 0.22
Development

No branches or pull requests
1 participant
@ocramz