Adjust return type for get_runtime_var_size_t to match use and name. #308
Conversation
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
Contributor
Author
|
As expected the c-extension linter warnings decreased from 25 to 21 with the four related warnings gone. |
jonasbardino
force-pushed
the
fix/pam-nss-c-ext-lint-size_t-vs-int-warnings
branch
4 times, most recently
from
da4c2b1 to
83cc40d
Compare
rasmunk
approved these changes
Aug 7, 2025
jonasbardino
force-pushed
the
fix/pam-nss-c-ext-lint-size_t-vs-int-warnings
branch
from
83cc40d to
c48a29e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Based on splint warnings: it looks like I simply forgot to adjust the return type to
type_twhen creating the function through copy/paste of the similarget_runtime_var_int.