Jonathan Grynspan
Jonathan Grynspan
Yes, this is a duplicate. It's not clear to me what the root cause is, but I imagine the core compiler team will know where to look.
Doesn't appear to be the same issue @cuberoot. I believe @plemarquand is taking a look.
> Might be nice to be able to capture output to stdout, stderr, and other file descriptors/streams, and compare those to expected output being written to them. Exit tests can...
My very rough thinking is that we'd allow developers to write an exit test that simulates invoking their CLI tool with a particular command line, and to have SAP use...
As I wrote there: > [@briancroom](https://forums.swift.org/u/briancroom), [@smontgomery](https://forums.swift.org/u/smontgomery), and I need to ~~squabble over~~ discuss it a bit more, but IMHO it is likely that we would treat the trait you...
You'd need to set `isRecursive` to `true` to have anything at all inherit the trait, but _what_ inherits the trait would be dependent on which protocols the type conforms to....
Which then may mean we want a tri- or quad-state here, not a boolean: ```swift enum Inheritance { case none case nestedTests case nestedSuites case allNestedThingies } var inheritance: Inheritance...
I'm going to redo this as an `enum` now that I have a better idea of the constraints we need to solve for.
That's not quite what we need here as we also distinguish dev builds.