You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Modern Swift compilers specialize generic code more eagerly under -O, particularly across module boundaries. This explodes binary size because every generic instantiation gets inlined and duplicated into client code.
Inlining Explosion
Swift’s optimizer (SILOptimizer) became more aggressive in inlining trivial wrappers, extensions, and computed properties — especially when annotated @inlinable or @usableFromInline.
Codegen Differences for ABI Stability
Swift’s stable ABI means your SDK is emitting extra symbols and metadata for resilience.
Under -O, the compiler prefers runtime speed (emitting duplicated type metadata and function bodies).
Under -Osize, it prunes these more aggressively.
Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
✨ Finishing touches🧪 Generate unit tests (beta)
Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch ci/resolve-binary-size-bloat
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
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.
TL;DR
StreamChat
to-Osize
and leftStreamChatUI
's one as it is:-O
.Test
What Changed in Swift 6.2 (Xcode 26)
Modern Swift compilers specialize generic code more eagerly under -O, particularly across module boundaries. This explodes binary size because every generic instantiation gets inlined and duplicated into client code.
Swift’s optimizer (SILOptimizer) became more aggressive in inlining trivial wrappers, extensions, and computed properties — especially when annotated @inlinable or @usableFromInline.
Swift’s stable ABI means your SDK is emitting extra symbols and metadata for resilience.
Under -O, the compiler prefers runtime speed (emitting duplicated type metadata and function bodies).
Under -Osize, it prunes these more aggressively.