Fix WebAssembly logging and CGFloat compatibility - #2
Draft
kudit wants to merge 1 commit into
Draft
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Purpose
Prepare Color for Compatibility 2.0 and fix the Swift Package Index WebAssembly issues seen in Color v1.5.2.
Current changes
@MainActormutableDebugLevel.colorLoggingstorage with a synchronous mutex-backed setting on Swift 6 so color parsing can read it from nonisolated code without forcingmain { ... }solely for configuration access.Remaining before merge
main { debug(...) }wrappers from CSS parsing where they existed only becausecolorLoggingwas MainActor-isolated.CGFloat: DoubleConvertibleon real CoreGraphics availability so WASM'sCGFloat = Doublealias does not redundantly reconformDouble.This stays draft until Compatibility 2.0.0 is available.