Stuart Montgomery

Do you get a different result if you first revert the change in swiftlang/swift-testing#690?

Thanks for those data points @ADKaster! Over to the swift repo to investigate the build failure further. CC @ahoppen @bnbarham for visibility

> I did see some interesting compiler warnings (visible in my gist in the initial post) about experimental features not being enabled as expected That's interesting to note. Here are...

> But `swift-testing` would need to update the reference here https://github.com/swiftlang/swift-testing/blob/83b0b049d6f73b58e05c0e3f1864c9b1db8b07b0/Sources/TestingMacros/CMakeLists.txt#L34 Thanks @rintaro ! I'll be happy to update that, once your fix lands in a new tag of swift-syntax.

> > But `swift-testing` would need to update the reference here https://github.com/swiftlang/swift-testing/blob/83b0b049d6f73b58e05c0e3f1864c9b1db8b07b0/Sources/TestingMacros/CMakeLists.txt#L34 > > Thanks @rintaro ! I'll be happy to update that, once your fix lands in a new...

@nmdias Can you gather a crash backtrace so we can confirm if it's the same issue?

@nmdias Thank you — yes, that crash log helps confirm that this is a different issue. I believe this may have been fixed by https://github.com/swiftlang/swift-testing/pull/787 (As an aside: that crash...

> Do you know if that fix already shipped in the latest Swift version? I don't believe that fix has shipped in any release yet. I can look into pulling...

Although the original reporter of this issue identified a workaround (explicitly typing the expression using `as`), I think we should pursue some kind macros enhancement to automate this, since users...

Thanks @etcwilde! This is a timely issue, since our GSoC contributor this summer is focusing on improvements in the console output experience. Providing some kind of summary or collected list...