Update Process.flag/2 specs#15602
Merged
Merged
Conversation
Member
|
The previous order was alphabetical, so I wonder if we should submit a PR to Erlang/OTP to keep it alphabetical. I'd prefer to keep it as that and only add the new specs. |
Contributor
Author
|
I ordered it in the same way as in the Erlang code because this func is delegate, and it also matches the order in the documentation. It seemed to me that this would make maintenance much easier as OTP evolves. So "keep it as that and only add the new specs"? |
Member
|
Let’s keep the alphabetical order. |
AlexGx
force-pushed
the
ag-process_flag_specs-fix
branch
from
July 14, 2026 08:53
d1748fb to
52dab79
Compare
Member
|
💚 💙 💜 💛 ❤️ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update
Process.flag/2specs.Specs have been reordered to match the order in which they appear in OTP doc.