eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

215
active users

#swiftlang

0 posts0 participants0 posts today
Continued thread
Continued thread

Bridging non-ASCII NSMutableStrings from ObjC will be slower at the point of bridging, *but* the String produced as a result will be much faster.

One particular case this tradeoff can end up not paying off in is if you then bridge the resulting String back to ObjC. If you're in that situation the recommendation is to not double-bridge strings if you can avoid it.

If you're in any other situation and this tradeoff is impacting your perf, please file a feedback.

Two obscure Swift changes I want to note:

ASCII String literals bridged to ObjC will produce a different type in the beta OSs. This should generally have no impact (other than greatly improved performance), but code incorrectly treating `NSString *` as `char *` may need to change (e.g. %s format strings).

A message will be logged in any situation we're applying compatibility workarounds for this, and the workaround will be disabled if you use the latest SDK version.