Update Assert and Julienne dependencies - #371
Merged
Merged
Conversation
These header files should hopefully never end up in a client's include path, but it doesn't hurt to go ahead and give them a unique name prefix.
This renames the module defined by the Assert library, to reduce the chance of linker symbols conflicts with client code.
Ensure FPM build artifacts land in an isolated directory
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR updates dependencies to the newly released versions of Assert and Julienne.
Together these should provide more robust integration for use cases outside our normal CI workflows (e.g. building a Julienne-enabled testsuite for a scientific library using flang
-fcoarrayand linking Caffeine and possibly a fourth-party assertions package).