Use interpolation instead of '+' concatenation for problematic expression #4123
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.
Goals ⚽
Reduces the type-checking time of a
debugDescription
variable by at least an order of magnitude.Implementation Details 🚧
Because type inference with
+
and literals has to do a lot of overload checking (for everyExpressibleBy____Literal
), many expressions which use+
for string concatenation with literals in contexts where type information is sparse may inadvertently cause a type checker performance explosion. In this case, we are concatenating an anonymous closure argument with a string literal, which caused a compilation time on the order of multiple seconds (on my MBP, YMMV). With this change, the type checking of this expression completes in under 100ms.Testing Details 🔍
There's no behavior change here. We could consider adding
-Xfrontend -warn-long-expression-type-checking=<limit>
to the Xcode project to catch warnings about type checker performance bottlenecks.