Fix compile errors for interpolated AnyVals #87
Merged
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.
The interpolation destructuring added in 3.6.0 attempts to convert interpolated messages to slf4j message formatting calls. These have signature
(String, Object*)Unit, and as such any interpolations involving value types result in compilation errors. The simplest fix I came up with for this is to invoketoStringon such interpolations, as they cannot be null.The implementation also doesn't escape
{}appearing in string parts, and doesn't account for Scala's wonky escape handling for interpolators.