4 ms·

> Perfectly valid code that used to work up till Xcode 11.1 throws errors in the Swift runtime on Xcode 11.2 (and 11.2.1) Can you link to some examples? I writ

• theFluke 7y ago
  Here's an example that I encountered recently: https://stackoverflow.com/questions/58657087/after-upgrading-to-xcode-11-2-from-xcode-11-1-app-crashes-due-to-uitextlayoutv https://stackoverflow.com/questions/58657087/after-upgrading...
  • saagarjha 7y ago
    To be fair, that's not an issue in the Swift runtime.
  • dep_b 7y ago
    That version of Xcode has been pulled because of this issue.
• Razengan 7y ago
  Type metadata accessor / failed to demangle superclass from mangled name: https://forums.swift.org/t/xcode-11-2-runtime-error-type-metadata-accessor-failed-to-demangle-superclass-from-mangled-name/30604 https://forums.swift.org/t/xcode-11-2-runtime-error-type-met... Property Wrapper initializers with #file/#function: https://forums.swift.org/t/compiler-segmentation-fault-when-using-property-wrappers-to-log-changes-to-a-value/30732 https://forums.swift.org/t/compiler-segmentation-fault-when-... With the disconnect between the Swift team and Apple after Swift going open-source, it's not clear if these goblins are spawned inside of Apple's APIs or the Swift runtime.