Why is the return value of String.addingPercentEncoding() optional?

后端 未结 2 929
醉话见心
醉话见心 2020-12-03 07:11

The signature of the String method for percent-escaping is:

func addingPercentEncoding(withAllowedCharacters: CharacterSet)
    -> String?


        
相关标签:
2条回答
  • 2020-12-03 07:24

    I filed a bug report with Apple about this, and heard back — with a very helpful response, no less!

    Turns out (much to my surprise) that it’s possible to successfully create Swift strings that contain invalid Unicode in the form of unpaired UTF-16 surrogate chars. Such a string can cause UTF-8 encoding to fail. Here’s some code that illustrates this behavior:

    // Succeeds (wat?!):
    let str = String(
        bytes: [0xD8, 0x00] as [UInt8],
        encoding: String.Encoding.utf16BigEndian)!
    
    // Returns nil:
    str.addingPercentEncoding(withAllowedCharacters:
        CharacterSet.alphanumerics)
    
    0 讨论(0)
  • 2020-12-03 07:29

    Based on Paul Cantrell answer, small demonstration that it's also possible for the same method to also return null in Objective-C, despite String and NSString being different beasts when it comes to encodings:

    uint8_t bytes[2] = { 0xD8, 0x00 };
    NSString *string = [[NSString alloc] initWithBytes:bytes length:2 encoding:NSUTF16BigEndianStringEncoding];
    // \ud800
    NSLog(@"%@", string);
    
    NSString *escapedString = [string stringByAddingPercentEncodingWithAllowedCharacters:NSCharacterSet.URLHostAllowedCharacterSet];
    // (null)
    NSLog(@"%@", escapedString);
    

    For fun, https://r12a.github.io/app-conversion/ will percent escape the same as:

    Error%20in%20convertUTF162Char%3A%20low%20surrogate%20expected%2C%20b%3D0%21%00

    0 讨论(0)
提交回复
热议问题