-
Notifications
You must be signed in to change notification settings - Fork 165
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
Prevent blist functions from modifying immutable blists (and several other kernel tweaks leading up to this) #3392
Conversation
6333a63
to
1118e6a
Compare
Codecov Report
@@ Coverage Diff @@
## master #3392 +/- ##
=========================================
Coverage ? 69.24%
=========================================
Files ? 633
Lines ? 305975
Branches ? 0
=========================================
Hits ? 211859
Misses ? 94116
Partials ? 0
|
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.
This looks good to me. I appreciated the separation in to four commits, it made reviewing it easy, thanks.
I'll add the |
1118e6a
to
f50f1f9
Compare
#3385 is now merged, so there's nothing stopping this PR from taking its purest form 🙂 |
The manual entry for e.g. `{}` refers to <poss>, as does the kernel code itself, so it seems sensible to adjust the error messages.
... where possible
f50f1f9
to
111d7df
Compare
I have now rebased this PR. I am not sure about the "purest form", though, it now also adds the mutability checks... I tried to break everything into "clean" commits, but let me know if you think it is too much and I should split it into two or more PRs. |
111d7df
to
ca9b062
Compare
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.
The separate commits make it easy to review, which I've done again, so I'm not bothered by the PR containing a few different types of changes.
If you think this resolves #3393 (which it seems to), then could you please make it so that merging this PR will close that issue?
This conflicts with PR #3385, so that PR should be merged first; after which I can rebase and update this PR.
But I wanted to put it out now, to make sure I don't leave it bitrotting here for another half year ;-).
Resolves #3393