Skip to content

Conversation

@topolarity
Copy link
Member

Someone more familiar with Julia than with C is not likely to recognize the significance of this error, but it's almost always a sign that you've built an object with a broken ABI somewhere.

I've also almost never seen this intentionally ignored in the wild, so I don't expect many false positives.

This is an easy thing to get wrong. Someone more familiar with Julia than
with C is not likely to recognize the significance of this error.

I've also almost never seen this intentionally ignored in the wild, so I
don't expect many false positives.
@topolarity
Copy link
Member Author

fwiw, @gbaraldi would like to compile with -Wall -Werror

I do like that hygiene, but it might need a flag since it's not uncommon to get warnings due to headers somewhat outside your control.

@sjkelly
Copy link
Collaborator

sjkelly commented Apr 4, 2024

fwiw, @gbaraldi would like to compile with -Wall -Werror

I think -Wall would be helpful.

@topolarity
Copy link
Member Author

Yeah, I agree - but let's tackle that in a separate PR to collect more input 👍

@topolarity topolarity merged commit 8e57908 into master Apr 4, 2024
@topolarity topolarity deleted the ct/error-implicit-fn-def branch April 4, 2024 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants