Ha, sorry to get to these in the wrong order. The real rule is "is the feature part of the Swift Open Source project", but certainly a normal Xcode user isn't thinking about whether the command they just used "came from Xcode" or "came from Swift".
Radars will always get to Apple Swift people if it turns out to be a Swift issue, but bugs.swift.org has fewer communication restrictions and allows non-Apple people to help. If it's not clearly a Swift issue ("the compiler crashed") or an Xcode issue ("I can't open my project"), it's a toss-up. But no harm done (and thanks for reporting the bug in the first place).
P.S. Why did I ask you to file the bug at bugreport.apple.com yourself? Because if I did it then you'd never hear when it was fixed, and wouldn't get the chance to test it on your own code and say "no, you fixed the wrong thing".
On Oct 3, 2016, at 10:12, Nate Birkholz via swift-users <firstname.lastname@example.org> wrote:
Then Jordan Rose closed it as not a Swift bug.
On Mon, Oct 3, 2016 at 2:03 AM, Alex Blewitt <email@example.com <mailto:firstname.lastname@example.org>> wrote:
On 30 Sep 2016, at 19:30, Nate Birkholz via swift-users <email@example.com <mailto:firstname.lastname@example.org>> wrote:
I found a bug in Swift 2.3 migration in the XCUITests, not sure if the bug goes to swift.org <http://swift.org/> or to Apple.
UI test generator uses the syntax (XCUIElement).children(matching: .other) but the compiler only recognizes childrenMatchingType(.Other), and you have to manually change the instances. Makes generating UI Tests a pain!
Please open a bug at https://bugs.swift.org <https://bugs.swift.org/> and then it can be re-routed if necessary. If you can attach the snippet of code with before/after that would help.
swift-users mailing list