Hi Ian,
Any place where the API differs should be marked with a comment like this:
/// - Experiment: This is a draft API currently under consideration for
official import into Foundation
If not, then we found some place that we either need to change or propose a
change for. We can track those
Hi Luke,
> On Jan 2, 2016, at 8:28 PM, Luke Howard via swift-corelibs-dev
> wrote:
>
> Many Foundation APIs use Int8 instead of CChar when representing C strings,
> e.g.:
> var UTF8String: UnsafePointer
>
As far as I understand NSURL is responsible for deallocating memory to
which UnsafePointer returned from NSURL.fileSystemRepresentation points to.
Could one use private buffer to store result
for NSURL.fileSystemRepresentation or layout of this class should be the
same as CFURL?
Also NSFileManager
OK, I filed [SR-466] as a compiler issue. If the behaviour changes and that
flows through to Darwin Foundation, we can update the open source one...
— Luke
> On 5 Jan 2016, at 8:21 AM, Philippe Hausler wrote:
>
> No C strings import as UnsafePointer for some reason; they
Hi Keith,
Also - the Xcode project is provided for development ease-of-use only. This
version of XCTest is only for non-Darwin platforms, and that builds with the
simple shell script that is in the root directory (build_script.py).
- Tony
> On Jan 4, 2016, at 9:19 AM, Daniel Dunbar via
Hi,
I came across hit issue while chaining filter() and prefix() on lazy
sequences:
https://bugs.swift.org/browse/SR-461
And started wondering if it would be more consistent if
lazy.filter().prefix() returned a custom
LazySequenceType instead of
Slice>.
That way