fix: resolve naming conflict with Foundation's Expression type #52
Conversation
This file contains 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
This commit resolves a naming conflict caused by the introduction of a new `Expression` type in the Foundation framework. By creating a private typealias for `Expression` that explicitly refers to `SQLite.Expression`, we ensure that our usage remains clear and unambiguous throughout the project.
|
Respectfully raising awareness about this very simple fix/issue. It blocks building with Xcode 16.0 Beta and would be great to have merged soon. |
|
@garriguv Any chance of getting this merged, please? |
|
@garriguv Please fix it as soon as possible. |
|
Up |
|
Thank you for the contribution |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 commit resolves a naming conflict caused by the introduction of a new
Expressiontype in the Foundation framework. By creating a private typealias forExpressionthat explicitly refers toSQLite.Expression, we ensure that our usage remains clear and unambiguous throughout the project.