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
refactor: auto-generate are_adjacent()
, avoid deprecated igraph_are_connected()
C function
#1254
Conversation
Current Aviator status
This PR was merged using Aviator.
See the real-time status of this PR on the
Aviator webapp.
Use the Aviator Chrome Extension
to see the status of your PR within GitHub.
|
a36caf1
to
4b5fd05
Compare
Thanks. Seeing
Could be a change in the build envionment, or related to this PR. New run for the main branch: https://github.com/igraph/rigraph/actions/runs/7946903820 |
Forgot to re-add a manual patch after auto-generation. |
4b5fd05
to
2211c0f
Compare
Fixed. |
Do we need two macros instead of one? |
CC @ntamas since he added this macro originally. I vote for changing the macro in the C core in the same way as above, as this warning has been a constant annoyance when testing with various compilers, and so far there has been no need for performing this NULL-check. But it should be decided by Tamás. |
I suspect it could be replaced with a static assert? |
That macro was the usual defensive programming habit from my side. If we can replace the check with a static assert, that's great. If we can't, let's add a runtime assert instead if possible. |
and no longer uses the deprecated `igraph_are_connected()`
2211c0f
to
7de8fc5
Compare
Fixes #1253