New FP Parsing: Use relevant part of a substring #86018
Conversation
|
@milseman I would appreciate if someone could double-check my use of internal String APIs here. In particular, I've not made any effort to test cases where a string is not "fast UTF8" capable; advice appreciated. |
|
This is a follow-on to #85797 |
| } else { | ||
| // Otherwise, make a copy so we have contiguous UTF8... | ||
| let string = String(text) | ||
| parsed = unsafe string._guts.withFastUTF8 { chars -> ${Self}? in |
There was a problem hiding this comment.
In particular, can I reliably assume that a copied string will always support withFastUTF8?
There was a problem hiding this comment.
Why not just use https://developer.apple.com/documentation/swift/string/makecontiguousutf8() ?
| expectNotNil(parsed) | ||
| expectEqual(parsed!.bitPattern, (2.0).bitPattern) | ||
| } | ||
|
|
There was a problem hiding this comment.
Do I need to test bridged strings specially here?
There was a problem hiding this comment.
I'm not going to turn down free test coverage of my code if it's offered, but I don't think it's at all necessary.
|
@swift-ci Please test |
2 participants
The new FP parsing code inadvertently used the entire backing string, even when the substring referred to just a portion.
This addresses a failure in the extended
UnicodeScalarProperties.swifttest, which parses an input file by reading a line into a String, then extracting Substrings. (rdar://166258748)