Re: [swift-corelibs-dev] Setting property "maxConcurrentOperationCount = 1" of NSOperation fails to execute operations using OpenSource Foundation.

2016-05-09 Thread Mamatha Busi via swift-corelibs-dev 
Dave
 
I am running the test-case on Mac but with the OpenSource Foundation source code. Just FYI if you missed the earlier conversation.
 
-Mamatha
 
- Original message -From: David P Grove/Watson/IBMTo: Philippe Hausler Cc: Mamatha Busi , swift-corelibs-dev@swift.orgSubject: Re: [swift-corelibs-dev] Setting property "maxConcurrentOperationCount = 1" of NSOperation fails to execute operations using OpenSource Foundation.Date: Fri, May 6, 2016 8:12 PM I think the intuition about the dispatch overlay being the problem on Linux is right on.  We may have to hack around the problem on the Foundation side until an improved overlay is available to use.--davePhilippe Hausler via swift-corelibs-dev ---05/06/2016 09:43:06 AM---I have a feeling this is associated with the changes for IUO types that recently landed. I am very wFrom: Philippe Hausler via swift-corelibs-dev To: Mamatha Busi Cc: swift-corelibs-dev@swift.orgDate: 05/06/2016 09:43 AMSubject: Re: [swift-corelibs-dev] Setting property "maxConcurrentOperationCount = 1" of NSOperation fails to execute operations using OpenSource Foundation.Sent by: swift-corelibs-dev-boun...@swift.org
I have a feeling this is associated with the changes for IUO types that recently landed. I am very worried that this actually could happen on Darwin targets as well. Perhaps it is the swift overlay for dispatch that is correcting the failure on Darwin and the dispatch on Linux is missing that annotation. Worth looking into.Sent from my iPhoneOn May 6, 2016, at 12:16 AM, Mamatha Busi  wrote:
 @ Philippe: Your right. Converting the 'attr' to an optional did do the job of creating a serial queue successfully. Thanks for that. I will create a PR for this. But this makes me think as to why until now, this was not caught by the compiler itself? RegardsMamatha 
- Original message -From: phaus...@apple.comTo: Mamatha Busi/India/IBM@IBMINCc: swift-corelibs-dev Subject: Re: [swift-corelibs-dev] Setting property "maxConcurrentOperationCount = 1" of NSOperation fails to execute operations using OpenSource Foundation.Date: Thu, May 5, 2016 10:54 PMHmm that seems unfortunate. I wonder if the serial creation is due to an unwrapped optional? var attr: dispatch_queue_attr_t? instead might do the trick… or alternatively we could just let the underlying queue be concurrent all the time and enforce the max ops via making the semaphore always instantiated (in the case of max ops being 1) and initializing it to 1 to gate the operations.  
On May 5, 2016, at 1:15 AM, Mamatha Busi via swift-corelibs-dev  wrote:  Hello 
Code snippet:
———
     let operation1 : NSBlockOperation = NSBlockOperation (block: {
            sleep(1)
            print("Opertion1")
        })
        let operation2 : NSBlockOperation = NSBlockOperation (block: {
            sleep(1)
            print("Opertion2”)
        })
        
        var operations = [NSOperation]()
        operations.append(operation1)
        operations.append(operation2)
 
        let queue = NSOperationQueue()
        queue.maxConcurrentOperationCount = 1
        queue.addOperations(operations, waitUntilFinished: true)
 
 
 
The above code snippet of adding operations to an operation queue and executing with the property ‘maxConcurrentOperationCount = 1’ fails while executing the above with the OpenSource Foundation and libDispatch of MAC inside Xcode. 
The error I am seeing is: 
fatal error: unexpectedly found nil while unwrapping an Optional value
Stack trace points to: attr = DISPATCH_QUEUE_SERIAL 
which implies that the libDispatch macro is coming as nil during the creation of the serial queue using libDispatch in the file NSOperationQueue
The same test-case passes on OSx. 
When I do not restrict the serial operation i.e. I remove ‘  queue.maxConcurrentOperationCount = 1’ , test case executes successfully.

Re: [swift-corelibs-dev] Change in String.CharacterView.Index?

2016-05-09 Thread Dennis Weissmann via swift-corelibs-dev 
Hey Joe,

The collection index model changed:

https://github.com/apple/swift-evolution/blob/master/proposals/0065-collections-move-indices.md

You now need to ask the collection for the next index:

let a = “Hello, World"
let secondIndex = a.characters.index(after: a.characters.startIndex)
print(a.characters[secondIndex]) // prints "e"

- Dennis

> On May 8, 2016, at 7:58 PM, Joseph Bell via swift-corelibs-dev 
>  wrote:
> 
> Howdy,
> 
> I've been building the latest Swift 3.0 and noticed that between Apr 25 and 
> today that String.CharacterView.Index.advance(by:) is no longer available.
> 
> This runs with an Apr 25 build (Swift 255544591c to be exact)
> let string:String = "Hello, world!"
> print(string.startIndex)
> print(string.startIndex.advanced(by:1))
> 
> It fails with a build today (May 8, Swift 26fcf1ab4a):
> test.swift:3:14: error: value of type 'Index' (aka 
> 'String.CharacterView.Index') has no member 'advanced'
> print(string.startIndex.advanced(by:1))
>   ~~~^~ 
> 
> I don't know who runs swiftdoc.org  but it is handy, 
> and shows advanced(by:) a valid method:
> http://swiftdoc.org/v3.0/type/String.CharacterView.Index/ 
> 
> 
> Not sure what I'm missing here!
> 
> Thanks,
> Joe
> 
> 
> -- 
> Joseph Bell
> http://dev.iachieved.it/iachievedit/ 
> @iachievedit
> ___
> swift-corelibs-dev mailing list
> swift-corelibs-dev@swift.org
> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev