Jonathan Grynspan
Jonathan Grynspan
We could have the convenience property on `TriviaPiece`, and then something "smarter" on `Trivia` that does the sort of work you're describing.
Not planning to do this for 6.2 as it's harmless as-is, we want to support 6.1 toolchains until 6.2 is released, and the compiler implementation hasn't fully settled yet. Will...
What's your thinking Stuart?
Sounds like a compiler bug that's conflicting with the 600.0.0 tag. We aren't seeing the compiler issue with the latest main-branch toolchain (our CI is happy.) We should send this...
> @grynspan Had a very interesting idea just now to reduce possible issues where the test index still has an old location for the test but it has been moved:...
Looks like a runtime crash. Forwarding to the runtime team to triage.
Some notes, in no particular order (will update if I think of more): - @stmontgomery's and my initial reaction is that this is probably _not_ related to Swift Testing since...
Type inference here is at the compiler level. Swift Testing receives an array of `[Any]` and doesn't have the opportunity to do its own type checking.
Type inference occurs before the `@Test` macro is expanded. There's nothing we can add that's in the language today that would tell the compiler to infer a type other than...
This is not something we can do in Swift Testing today because the failure happens _before_ macro expansion (because the type inference on the array resolves to `[Any]` instead of...