I just tried it myself with a framework and app target and it worked. Can you reproduce what you’re seeing in a simple project and file a bug report at https://bugs.swift.org <https://bugs.swift.org/> ?
Sorry for the trouble! Jordan > On Sep 6, 2017, at 13:35, Howard Lovatt <howard.lov...@gmail.com> wrote: > > I have a custom operator defined in a module and in my XCTest I import that > module. In the tests the compiler says that the operator isn't defined. If I > define the operator manually in the tests then it works. > > So what is going on? > > -- Howard. > > On 7 Sep 2017, at 3:45 am, Jordan Rose <jordan_r...@apple.com > <mailto:jordan_r...@apple.com>> wrote: > >> It's actually the other way around: all operator declarations are exported >> from a module, all the time, even if the functions that implement them >> aren't. This is probably a model we should improve, but it's been that way >> since Swift 1. >> >> Jordan >> >> >>> On Sep 6, 2017, at 02:08, Howard Lovatt via swift-users >>> <swift-users@swift.org <mailto:swift-users@swift.org>> wrote: >>> >>> Hi All, >>> >>> I am trying to use a custom operator imported from a module, unfortunately >>> you can't add public to the operators definition and therefore it isn't >>> exported from the module. >>> >>> I can manually redefine the operator in the module where the operator is >>> used, but that isn't very satisfactory - is there a better way? >>> >>> Thanks in advance, >>> >>> -- Howard. >>> _______________________________________________ >>> swift-users mailing list >>> swift-users@swift.org <mailto:swift-users@swift.org> >>> https://lists.swift.org/mailman/listinfo/swift-users >>> <https://lists.swift.org/mailman/listinfo/swift-users> >>
_______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
