Looks like our continuous integration server works fine:
https://github.com/apple/swift-corelibs-xctest/pull/132
Madhu, are you sure you're using the latest master branch commit on each of
the apple/swift repositories? Specifically, you should pull down the latest
changes on: swift, swift-llvm,
Frankly, I think I just forgot to put a stub for it when we put out the first
set of APIs.
- Tony
> On Jul 5, 2016, at 4:54 PM, Luke Howard wrote:
>
> I added NSLog for NSKeyedArchiver so the output formatting would more closely
> match Darwin, but I punted whether to make it
I added NSLog for NSKeyedArchiver so the output formatting would more closely
match Darwin, but I punted whether to make it public.
> On 6 Jul 2016, at 5:42 AM, Tony Parker via swift-corelibs-dev
> wrote:
>
> Hi Sai,
>
> Out of curiosity, why NSLog instead of
Hi Sai,
Out of curiosity, why NSLog instead of Swift’s print function?
- Tony
> On Jun 27, 2016, at 4:37 AM, Sai Kanduri via swift-corelibs-dev
> wrote:
>
> Hi All,
>
> Currently NSLog has only one internal function NSLog() which can be used
> only by
Hmm, it does look like XCTest needs some work done to get things working
with the latest Swift 3 changes made in the stdlib and corelibs-foundation.
I don't have access to a development environment to investigate further,
but as far as I can tell, this wouldn't build on Linux either. Has there