Greg Cotten
Greg Cotten
I've decided to incorporate the string literal handling of [swift-macro-toolkit](https://github.com/stackotter/swift-macro-toolkit?tab=readme-ov-file#get-the-value-of-a-string-literal) to make the string literal interpretation more robust. Escape characters like "\u{2020}" were being incorrectly interpreted as literals on `main`.
OK I believe I am actually done with this PR now, if you want to take a look.
@p-x9 let me know what you think. Just to be clear, the **current behavior** of the macro is that it will interpret string interpolation as a literal and not fail....
Any chance you'll pull this in anytime soon? @p-x9
turns out there was a way in `SwiftParser` to handle the string literals correctly, so I've removed the `swift-macro-toolkit` dependency. Hopefully that makes things a lot cleaner!
Yes this PR is finished! Yes, please tag a new release too.
https://github.com/swhitty/FlyingFox is the solution, I think!
Maybe even like this? Where the first conditional statement is on a newline. ```swift guard let keyboardAnimationCurve = (dictionary[UIResponder.keyboardAnimationCurveUserInfoKey] as? NSNumber).flatMap({ UIView.AnimationCurve(rawValue: $0.intValue) }), let keyboardAnimationDuration = dictionary[UIResponder.keyboardAnimationDurationUserInfoKey] as? NSNumber,...
Interesting! I guess my issue with `path` being RFC8089 is that it's a rather large change, especially for me :) I often use `someURL.path` as a way of communicating a...
Works for me on the Windows 6.0.2 x86_64 release toolchain available on https://swift.org/download