forked from CoreOffice/XMLCoder
-
Notifications
You must be signed in to change notification settings - Fork 0
v1.0.0-alpha.1 #2
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Verify Sendable compliance with DateFormatter case.
While adding
Sendableconformance toDateBoxis good for concurrency safety, theFormat.formatter(DateFormatter)case may be problematic sinceDateFormatteris notSendable. This could lead to compiler warnings or errors in strict concurrency mode.Let me verify if
DateFormatterconforms toSendable:🏁 Script executed:
Length of output: 117
Let’s inspect the
Formatenum in DateBox.swift to confirm itsSendableconformance and associated cases:🏁 Script executed:
Length of output: 345
Fix the non-Sendable
DateFormattercase inDateBox.Format.The
Format.formatter(DateFormatter)associated value makesFormat(and thusDateBox) fail strict-Sendablechecks, sinceDateFormatterisn’tSendable. To resolve this, either:DateFormatter–based case with a thread-safe alternative (e.g. a format identifier or closure that’sSendable),@unchecked Sendable.For example, at the bottom of Sources/XMLCoder/Auxiliaries/Box/DateBox.swift:
enum Format: Equatable { case secondsSince1970 case millisecondsSince1970 case iso8601 case formatter(DateFormatter) } + + // DateFormatter is not @Sendable; opt out of checking here + @unchecked + extension DateBox.Format: Sendable {}• Location to update:
🤖 Prompt for AI Agents