-
Notifications
You must be signed in to change notification settings - Fork 37
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
[pub_semver] Discourage modification of properties intended to be unmodifiable #2020
base: main
Are you sure you want to change the base?
Conversation
PR HealthBreaking changes ✔️
Changelog Entry ✔️
Changes to files need to be accounted for in their respective changelogs. Coverage ✔️
This check for test coverage is informational (issues shown here will not fail the PR). API leaks ✔️The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.
License Headers ✔️
All source files should start with a license header. Unrelated files missing license headers
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as #2021 I'm not sure the potential slight breakage is worth the benefits of slightly lower memory pressure.
Do we have situations where the memory consumption of Version objects is significant or causing problems?
I think that's fair. I've instead repurposed the PR to discourage modification in the doc comments and changelog. I doubt anyone is doing so right now anyway, but if they are, hopefully this can help avoid new usages and make the change easier to make in the future. |
holy cow, great find @parlough |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI -
No description provided.