Update for Swift 5.8 support

[thedavidharris]

Fixes a few build errors on Xcode 14.3

[kean]

I'm surprised else if let wasn't producing a warning. Thanks!

But can you please explain what changed with regex literals in Swift 5.8? I can't seem to find any references. I don't see I saw any deprecations for the "bare /" syntax.

I just learned about extended delimiters thanks to the PR. It will make sense to replace some regexes:

// Before
 /(.*?) · 200 OK · GET https:\/\/example.com\/api\n/

// After
 #/(.*?) · 200 OK · GET https://example.com/api\n/#

[thedavidharris]

But can you please explain what changed with regex literals in Swift 5.8? I can't seem to find any references. I don't see I saw any deprecations for the "bare /" syntax.

I couldn't find anything either, was wondering if you might know from looking at this. For whatever reason it wouldn't compile and pick up the regex literal even when extracting to a separate variable.

[thedavidharris]

I think it's just behind a flag now: https://github.com/apple/swift/blob/c82e17acb7d54fad674699b9c9b2804203d5a992/include/swift/Option/Options.td#L721. -enable-upcoming-feature BareSlashRegexLiterals would also do it in Xcode.

Unsure why that was working before though.