Added NSPipe implementation

CONTRIBUTING.md

@@ -1,6 +1,11 @@
 # Contributing
 
-Contributions to Foundation are welcome! This project follows the [contribution guidelines for the Swift project](https://swift.org/contributing/#reporting-bugs). A few additional details are outlined below.
+Contributions to Foundation are welcome! This project follows the [contribution guidelines for the Swift project](https://swift.org/contributing/#contributing-code). A few additional details are outlined below.
+
+## Licensing
+
+By submitting a pull request, you represent that you have the right to license your contribution to Apple and the community, and agree by submitting the patch that your contributions are licensed under the [Swift license](https://swift.org/LICENSE.txt).
+
 
 ## Bug Reports
 

CoreFoundation/NumberDate.subproj/CFNumber.c

@@ -1099,6 +1099,7 @@ static inline void _CFNumberInit(CFNumberRef result, CFNumberType type, const vo
         case kCFNumberFloat32Type: memmove((void *)&result->_pad, valuePtr, 4); break;
         case kCFNumberFloat64Type: memmove((void *)&result->_pad, valuePtr, 8); break;
     }
+    __CFBitfieldSetValue(((struct __CFNumber *)result)->_base._cfinfo[CF_INFO_BITS], 4, 0, (uint8_t)__CFNumberTypeTable[type].canonicalType);
 }
 
 CF_EXPORT void _CFNumberInitBool(CFNumberRef result, Boolean value) {

Docs/Design.md

@@ -13,6 +13,8 @@ In a very limited number of cases, key Foundation API as it exists on Apple plat
 
 A significant portion of the implementation of Foundation on Apple platforms is provided by another framework called CoreFoundation (a.k.a. CF). CF is written primarily in C and is very portable. Therefore we have chosen to use it for the internal implementation of Swift Foundation where possible. As CF is present on all platforms, we can use it to provide a common implementation everywhere.
 
+Another aspect of portability is keeping dependencies to an absolute minimum. With fewer dependencies to port, it is more likely that Foundation will be able to easily compile and run on new platforms. Therefore, we will prefer solutions that are implemented in Foundation itself. Exceptions can be made for major functionality (for example, `ICU`, `libdispatch`, and `libxml2`).
+
 ## A Taxonomy of Types
 
 A key to the internal design of the framework is the split between the CF implementation and Swift implementation of the Foundation classes. They can be organized into several categories.

Docs/GettingStarted.md

@@ -12,7 +12,7 @@ In order to build on OS X, you will need:
 
 Foundation is developed at the same time as the rest of Swift, so the most recent version of the compiler is required in order to build it.
 
-The repository includes an Xcode project file as well as an Xcode workspace. The workspace includes both Foundation and XCTest, which makes it easy to build and run everything together. The workspace assumes that Foundation and XCTest are checked out from GitHub in peer directories. For example:
+The repository includes an Xcode project file as well as an Xcode workspace. The workspace includes both Foundation and XCTest, which makes it easy to build and run everything together. The workspace assumes that Foundation and XCTest are checked out from GitHub in sibling directories. For example:
 
 ```
 % cd Development
@@ -25,7 +25,7 @@ Build and test steps:
 
 0. Run Xcode with the latest toolchain. Follow [the instructions here](https://swift.org/download/#apple-platforms) to start Xcode with the correct toolchain.
 0. Open `Foundation.xcworkspace`.
-0. Build the _Foundation_ target. This builds CoreFoundation and Foundation.
+0. Build the _SwiftFoundation_ target. This builds CoreFoundation and Foundation.
 0. Run (Cmd-R) the _TestFoundation_ target. This builds CoreFoundation, Foundation, XCTest, and TestFoundation, then runs the tests.
 
 > Note: If you see the name of the XCTest project file in red in the workspace, then Xcode cannot find the cloned XCTest repository. Make sure that it is located next to the `swift-corelibs-foundation` directory and has the name `swift-corelibs-xctest`.
@@ -74,3 +74,11 @@ LD_LIBRARY_PATH=../build/Ninja-ReleaseAssert/foundation-linux-x86_64/Foundation/
 ```
 
 Just copy & paste the correct line.
+
+When new source files or flags are added to the `build.py` script, the project will need to be reconfigured in order for the build system to pick them up. The top-level `swift/utils/build-script` can be used, but for quicker iteration you can use the following command to limit the reconfiguration to just the Foundation project:
+
+```
+% ninja reconfigure
+% ninja
+```
+

Foundation/NSCalendar.swift

@@ -365,11 +365,7 @@ public class NSCalendar : NSObject, NSCopying, NSSecureCoding {
     public func dateFromComponents(comps: NSDateComponents) -> NSDate? {
         var (vector, compDesc) = _convert(comps)
 
-        let oldTz = timeZone
-        let tempTz = comps.timeZone
-        if let tz = tempTz {
-            timeZone = tz
-        }
+        self.timeZone = comps.timeZone ?? timeZone
 
         var at: CFAbsoluteTime = 0.0
         let res: Bool = withUnsafeMutablePointer(&at) { t in
@@ -378,15 +374,11 @@ public class NSCalendar : NSObject, NSCopying, NSSecureCoding {
             }
         }
 
-        if tempTz != nil {
-            self.timeZone = oldTz
-        }
-
         if res {
             return NSDate(timeIntervalSinceReferenceDate: at)
+        } else {
+            return nil
         }
-
-        return nil
     }
 
     private func _setup(unitFlags: NSCalendarUnit, field: NSCalendarUnit, type: String, inout compDesc: [Int8]) {

Foundation/NSData.swift

@@ -414,6 +414,28 @@ extension NSData {
         }
     }
 
+    public func writeToFile(path: String, atomically useAuxiliaryFile: Bool) -> Bool {
+        do {
+            try writeToFile(path, options: useAuxiliaryFile ? .DataWritingAtomic : [])
+        } catch {
+            return false
+        }
+        return true
+    }
+
+    public func writeToURL(url: NSURL, atomically: Bool) -> Bool {
+        if url.fileURL {
+            if let path = url.path {
+                return writeToFile(path, atomically: atomically)
+            }
+        }
+        return false
+    }
+
+    public func writeToURL(url: NSURL, options writeOptionsMask: NSDataWritingOptions) throws {
+        NSUnimplemented()
+    }
+
     internal func enumerateByteRangesUsingBlockRethrows(block: (UnsafePointer<Void>, NSRange, UnsafeMutablePointer<Bool>) throws -> Void) throws {
         var err : ErrorType? = nil
         self.enumerateByteRangesUsingBlock() { (buf, range, stop) -> Void in
@@ -482,6 +504,33 @@ public class NSMutableData : NSData {
     }
 }
 
+extension NSData {
+
+    /* Create an NSData from a Base-64 encoded NSString using the given options. By default, returns nil when the input is not recognized as valid Base-64.
+    */
+    public convenience init?(base64EncodedString base64String: String, options: NSDataBase64DecodingOptions) {
+        NSUnimplemented()
+    }
+
+    /* Create a Base-64 encoded NSString from the receiver's contents using the given options.
+    */
+    public func base64EncodedStringWithOptions(options: NSDataBase64EncodingOptions) -> String {
+        NSUnimplemented()
+    }
+
+    /* Create an NSData from a Base-64, UTF-8 encoded NSData. By default, returns nil when the input is not recognized as valid Base-64.
+    */
+    public convenience init?(base64EncodedData base64Data: NSData, options: NSDataBase64DecodingOptions) {
+        NSUnimplemented()
+    }
+
+    /* Create a Base-64, UTF-8 encoded NSData from the receiver's contents using the given options.
+    */
+    public func base64EncodedDataWithOptions(options: NSDataBase64EncodingOptions) -> NSData {
+        NSUnimplemented()
+    }
+}
+
 extension NSMutableData {
 
     public func appendBytes(bytes: UnsafePointer<Void>, length: Int) {

Foundation/NSDecimalNumber.swift

@@ -9,10 +9,10 @@
 
 
 /***************	Exceptions		***********/
-public let NSDecimalNumberExactnessException: String = "" // NSUnimplemented
-public let NSDecimalNumberOverflowException: String = "" // NSUnimplemented
-public let NSDecimalNumberUnderflowException: String = "" // NSUnimplemented
-public let NSDecimalNumberDivideByZeroException: String = "" // NSUnimplemented
+public let NSDecimalNumberExactnessException: String = "NSDecimalNumberExactnessException"
+public let NSDecimalNumberOverflowException: String = "NSDecimalNumberOverflowException"
+public let NSDecimalNumberUnderflowException: String = "NSDecimalNumberUnderflowException"
+public let NSDecimalNumberDivideByZeroException: String = "NSDecimalNumberDivideByZeroException"
 
 /***************	Rounding and Exception behavior		***********/
 

Foundation/NSFileManager.swift

@@ -211,12 +211,13 @@ public class NSFileManager : NSObject {
 
         This method replaces fileAttributesAtPath:traverseLink:.
      */
-    public func attributesOfItemAtPath(path: String) throws -> [String : AnyObject] {
+    /// - Experiment: Note that the return type of this function is different than on Darwin Foundation (Any instead of AnyObject). This is likely to change once we have a more complete story for bridging in place.
+    public func attributesOfItemAtPath(path: String) throws -> [String : Any] {
         var s = stat()
         guard lstat(path, &s) == 0 else {
             throw _NSErrorWithErrno(errno, reading: true, path: path)
         }
-        var result = [String : AnyObject]()
+        var result = [String : Any]()
         result[NSFileSize] = NSNumber(unsignedLongLong: UInt64(s.st_size))
 
 #if os(OSX) || os(iOS)
@@ -233,14 +234,14 @@ public class NSFileManager : NSObject {
 
         let pwd = getpwuid(s.st_uid)
         if pwd != nil && pwd.memory.pw_name != nil {
-            if let name = NSString(bytes: pwd.memory.pw_name, length: Int(strlen(pwd.memory.pw_name)), encoding: NSUTF8StringEncoding) {
+            if let name = String.fromCString(pwd.memory.pw_name) {
                 result[NSFileOwnerAccountName] = name
             }
         }
 
         let grd = getgrgid(s.st_gid)
         if grd != nil && grd.memory.gr_name != nil {
-            if let name = NSString(bytes: grd.memory.gr_name, length: Int(strlen(grd.memory.gr_name)), encoding: NSUTF8StringEncoding) {
+            if let name = String.fromCString(grd.memory.gr_name) {
                 result[NSFileGroupOwnerAccountID] = name
             }
         }
@@ -255,7 +256,7 @@ public class NSFileManager : NSObject {
             case S_IFSOCK: type = NSFileTypeSocket
             default: type = NSFileTypeUnknown
         }
-        result[NSFileType] = NSString(type)
+        result[NSFileType] = type
 
         if type == NSFileTypeBlockSpecial || type == NSFileTypeCharacterSpecial {
             result[NSFileDeviceIdentifier] = NSNumber(unsignedLongLong: UInt64(s.st_rdev))

Foundation/NSIndexPath.swift

@@ -15,10 +15,7 @@ public class NSIndexPath : NSObject, NSCopying, NSSecureCoding {
         _indexes = []
     }
     public init(indexes: UnsafePointer<Int>, length: Int) {
-        _indexes = []
-        for var idx = 0; idx < length; idx++ {
-            _indexes.append(indexes[idx])
-        }
+        _indexes = Array(UnsafeBufferPointer(start: indexes, count: length))
     }
 
     private init(indexes: [Int]) {

Foundation/NSIndexSet.swift

@@ -13,17 +13,17 @@
 The following code snippets can be used to enumerate over the indexes in an NSIndexSet:
 
     // Forward
-    NSUInteger currentIndex = [set firstIndex];
-    while (currentIndex != NSNotFound) {
+    var currentIndex = set.firstIndex
+    while currentIndex != NSNotFound {
         ...
-        currentIndex = [set indexGreaterThanIndex:currentIndex];
+        currentIndex = set.indexGreaterThanIndex(currentIndex)
     }
-    
+
     // Backward
-    NSUInteger currentIndex = [set lastIndex];
-    while (currentIndex != NSNotFound) {
+    var currentIndex = set.lastIndex
+    while currentIndex != NSNotFound {
         ...
-        currentIndex = [set indexLessThanIndex:currentIndex];
+        currentIndex = set.indexLessThanIndex(currentIndex)
     }
 
 To enumerate without doing a call per index, you can use the method getIndexes:maxCount:inIndexRange:.
@@ -484,12 +484,10 @@ public class NSMutableIndexSet : NSIndexSet {
     }
 
     public func addIndex(value: Int) {
-        // TODO: Bounds checking
         self.addIndexesInRange(NSMakeRange(value, 1))
     }
 
     public func removeIndex(value: Int) {
-        // TODO: Bounds checking
         self.removeIndexesInRange(NSMakeRange(value, 1))
     }
 

Foundation/NSPort.swift

@@ -10,7 +10,7 @@
 
 public typealias NSSocketNativeHandle = Int32
 
-public let NSPortDidBecomeInvalidNotification: String = "" // NSUnimplemented
+public let NSPortDidBecomeInvalidNotification: String = "NSPortDidBecomeInvalidNotification"
 
 public class NSPort : NSObject, NSCopying, NSCoding {
 

Foundation/NSProgress.swift

@@ -154,35 +154,35 @@ public protocol NSProgressReporting : NSObjectProtocol {
 
 /* How much time is probably left in the operation, as an NSNumber containing a number of seconds.
 */
-public let NSProgressEstimatedTimeRemainingKey: String = "" // NSUnimplemented
+public let NSProgressEstimatedTimeRemainingKey: String = "NSProgressEstimatedTimeRemainingKey"
 
 /* How fast data is being processed, as an NSNumber containing bytes per second.
 */
-public let NSProgressThroughputKey: String = "" // NSUnimplemented
+public let NSProgressThroughputKey: String = "NSProgressThroughputKey"
 
 /* The value for the kind property that indicates that the work being done is one of the kind of file operations listed below. NSProgress of this kind is assumed to use bytes as the unit of work being done and the default implementation of -localizedDescription takes advantage of that to return more specific text than it could otherwise. The NSProgressFileTotalCountKey and NSProgressFileCompletedCountKey keys in the userInfo dictionary are used for the overall count of files.
 */
-public let NSProgressKindFile: String = "" // NSUnimplemented
+public let NSProgressKindFile: String = "NSProgressKindFile"
 
 /* A user info dictionary key, for an entry that is required when the value for the kind property is NSProgressKindFile. The value must be one of the strings listed in the next section. The default implementations of of -localizedDescription and -localizedItemDescription use this value to determine the text that they return.
 */
-public let NSProgressFileOperationKindKey: String = "" // NSUnimplemented
+public let NSProgressFileOperationKindKey: String = "NSProgressKindFile"
 
 /* Possible values for NSProgressFileOperationKindKey entries.
 */
-public let NSProgressFileOperationKindDownloading: String = "" // NSUnimplemented
-public let NSProgressFileOperationKindDecompressingAfterDownloading: String = "" // NSUnimplemented
-public let NSProgressFileOperationKindReceiving: String = "" // NSUnimplemented
-public let NSProgressFileOperationKindCopying: String = "" // NSUnimplemented
+public let NSProgressFileOperationKindDownloading: String = "NSProgressFileOperationKindDownloading"
+public let NSProgressFileOperationKindDecompressingAfterDownloading: String = "NSProgressFileOperationKindDecompressingAfterDownloading"
+public let NSProgressFileOperationKindReceiving: String = "NSProgressFileOperationKindReceiving"
+public let NSProgressFileOperationKindCopying: String = "NSProgressFileOperationKindCopying"
 
 /* A user info dictionary key. The value must be an NSURL identifying the item on which progress is being made. This is required for any NSProgress that is published using -publish to be reported to subscribers registered with +addSubscriberForFileURL:withPublishingHandler:.
 */
-public let NSProgressFileURLKey: String = "" // NSUnimplemented
+public let NSProgressFileURLKey: String = "NSProgressFileURLKey"
 
 /* User info dictionary keys. The values must be NSNumbers containing integers. These entries are optional but if they are both present then the default implementation of -localizedAdditionalDescription uses them to determine the text that it returns.
 */
-public let NSProgressFileTotalCountKey: String = "" // NSUnimplemented
-public let NSProgressFileCompletedCountKey: String = "" // NSUnimplemented
+public let NSProgressFileTotalCountKey: String = "NSProgressFileTotalCountKey"
+public let NSProgressFileCompletedCountKey: String = "NSProgressFileCompletedCountKey"
 
 
 

Foundation/NSRunLoop.swift

@@ -8,8 +8,8 @@
 //
 
 
-public let NSDefaultRunLoopMode: String = "" // NSUnimplemented
-public let NSRunLoopCommonModes: String = "" // NSUnimplemented
+public let NSDefaultRunLoopMode: String = "NSDefaultRunLoopMode"
+public let NSRunLoopCommonModes: String = "NSRunLoopCommonModes"
 
 public class NSRunLoop : NSObject {
 

Foundation/NSURLError.swift

@@ -12,20 +12,20 @@
     @discussion Constants used by NSError to differentiate between "domains" of error codes, serving as a discriminator for error codes that originate from different subsystems or sources.
     @constant NSURLErrorDomain Indicates an NSURL error.
 */
-public let NSURLErrorDomain: String = "" // NSUnimplemented
+public let NSURLErrorDomain: String = "NSURLErrorDomain"
 
 /*!
     @const NSURLErrorFailingURLErrorKey
     @abstract The NSError userInfo dictionary key used to store and retrieve the URL which caused a load to fail.
 */
-public let NSURLErrorFailingURLErrorKey: String = "" // NSUnimplemented
+public let NSURLErrorFailingURLErrorKey: String = "NSErrorFailingURLKey"
 
 /*!
     @const NSURLErrorFailingURLStringErrorKey
     @abstract The NSError userInfo dictionary key used to store and retrieve the NSString object for the URL which caused a load to fail.
     @discussion This constant supersedes NSErrorFailingURLStringKey, which was deprecated in Mac OS X 10.6.  Both constants refer to the same value for backward-compatibility, but this symbol name has a better prefix.
 */
-public let NSURLErrorFailingURLStringErrorKey: String = "" // NSUnimplemented
+public let NSURLErrorFailingURLStringErrorKey: String = "NSErrorFailingURLStringKey"
 
 /*!
     @const NSErrorFailingURLStringKey
@@ -37,14 +37,14 @@ public let NSURLErrorFailingURLStringErrorKey: String = "" // NSUnimplemented
     @const NSURLErrorFailingURLPeerTrustErrorKey
     @abstract The NSError userInfo dictionary key used to store and retrieve the SecTrustRef object representing the state of a failed SSL handshake.
  */
-public let NSURLErrorFailingURLPeerTrustErrorKey: String = "" // NSUnimplemented
+public let NSURLErrorFailingURLPeerTrustErrorKey: String = "NSURLErrorFailingURLPeerTrustErrorKey"
 
 /*!
     @const NSURLErrorBackgroundTaskCancelledReasonKey
     @abstract The NSError userInfo dictionary key used to store and retrieve the NSNumber corresponding to the reason why a background
 	NSURLSessionTask was cancelled
  */
-public let NSURLErrorBackgroundTaskCancelledReasonKey: String = "" // NSUnimplemented
+public let NSURLErrorBackgroundTaskCancelledReasonKey: String = "NSURLErrorBackgroundTaskCancelledReasonKey"
 
 /*!
     @enum Codes associated with NSURLErrorBackgroundTaskCancelledReasonKey