-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix calls in caffeine.c
#108
Conversation
The following two warnings still exist because when attempting to remove the warnings by dereferencing the
|
I suspect you deployed the wrong fix. This is a warning about mismatched types in code that is already believed to operate correctly. In such a situation adding or removing a deference operator to assuage the typechecker is almost never the right fix, because it changes the semantics of the code that already runs correctly (to something that usually does not). I believe the actual problem here is with the type declarations, specifically the C declaration of the |
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.
Code changes so far look right.
I agree there are several problems revealed in issue #74 that remain unaddressed so far. I'd say it's your choice whether to merge this incremental improvement as-is, or attempt to fix the rest of the warnings here.
On a related note, I'd like to suggest/request a convention where commits which fix or address issues include the issue number in the commit message. Right now the issue number appears only in the PR description, but years from now it will be much easier to understand the commit in isolation if the issue number also appears in the commit message.
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.
Looks fine to me, but I'll defer to Dan on the intricacies of C type-casting.
Closes #74.