Fix build when Z3_API macro is non-empty #7553
Merged
Conversation
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
API function definitions are updated to be consistent with header files.
|
@microsoft-github-policy-service agree |
arbipher
pushed a commit
to arbipher/z3
that referenced
this pull request
Apr 17, 2025
API function definitions are updated to be consistent with header files.
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.
Z3 fails to build with VS 2022 when the macro
Z3_APIis defined as__stdcalldue to differences between API function declarations and definitions. This PR updates function definitions to match declarations byZ3_APImacro where missing;Z3_API char const *toZ3_string Z3_API.