Skip to content

Conversation

@Enchufa2
Copy link
Member

Closes #1400. As discussed there, technically __has_include was introduced in C++17, but in practice, being a preprocessor macro, compilers define it regardless of the standard set (tested locally with gcc and clang). Also, checking whether __has_include is defined first is safer as recommended by gcc.

Checklist

  • Code compiles correctly
  • R CMD check still passes all tests
  • Preferably, new tests were added which fail without the change
  • Document the changes by file in ChangeLog

Copy link
Member

@eddelbuettel eddelbuettel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks good to me

@Enchufa2 Enchufa2 merged commit 9f07c76 into master Oct 22, 2025
26 checks passed
@Enchufa2 Enchufa2 deleted the fix/musl branch October 22, 2025 08:46
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.

switch to a whitelist for #include <execinfo.h>

2 participants