Hm, I’ll have to defer to Mike on the status of this one.
If it’s not in place now, we should probably schedule it for a future release.
- Tony
> On Jul 29, 2016, at 11:43 AM, Brian Gesiak wrote:
>
> Thanks for the heads up, Tony!
>
> (+cc corelibs-xctest release manager Mike Ferris)
> Just t
Thanks for the heads up, Tony!
(+cc corelibs-xctest release manager Mike Ferris)
Just to confirm, we are not resolving https://bugs.swift.org/browse/SR-710,
"Generate XCTestCaseProvider entries on Linux", in time for the Swift 3
release. Is this correct?
- Brian Gesiak
On Fri, Jul 29, 2016 at 2
Hi Gonzalo,
While not a complete solution for the issues around bridging, the work on
id-as-Any that I mentioned below was meant to help address these platform
differences.
For example, let’s say you had a Foundation API that looked like this in ObjC:
- (void)foo:(id)x;
and imported like this
Hi everyone,
Wanted to know if there's any plan to find a solution for Auto Bridging
between corelibs-foundation <> Swift types in the same manner as it is done
for Obj-C.
There has been some discussions about this in the following PRs:
https://github.com/apple/swift-corelibs-foundation/pull/310
I received some feedback from Paulo Faria that I’d like to share here:
Is there a way to change the performance test baselines by code? I can’t
find a way to do it today. So my question would be, why can’t we set the
baselines by code? Is it because we need a different baseline for each
different
