Re: [swift-corelibs-dev] Need of inputs for NSExpression

[Tony Parker via swift-corelibs-dev]

Hi Pushkar,

> On Jan 16, 2017, at 12:26 AM, Pushkar N Kulkarni  
> wrote:
> 
> Hi Tony, 
> 
> I have a question. 
> 
> >> Some of it is pretty tricky to implement without the dynamic behavior of 
> >> ObjC though.
> I guess you were referring to something like 
> "NSExpression(format:"FUNCTION(4.2, 'factorial')")" where `factorial` is a 
> function defined on an extension of NSNumber. Now, this translation of a 
> string to a function handle/pointer seems quite intimidating to me, in the 
> Swift context :-) 
> Are there any known approaches? Is there any kind of general guidance you'd 
> give here? 

Yah, that’s the problematic bit.

With Objective-C, we have a whole host of API that allows dynamic lookup of 
selectors, classes, etc. None of that exists on Linux, and I don’t think we 
have any reasonable replacement.

- Tony

> 
> Thank you!
> 
> Pushkar N Kulkarni,
> IBM Runtimes
> 
> Simplicity is prerequisite for reliability - Edsger W. Dijkstra
> 
> 
> 
> -swift-corelibs-dev-boun...@swift.org 
>  wrote: -
> To: Nethra Ravindran  >
> From: Tony Parker via swift-corelibs-dev 
> Sent by: swift-corelibs-dev-boun...@swift.org 
> 
> Date: 01/12/2017 09:44PM
> Cc: swift-corelibs-dev@swift.org 
> Subject: Re: [swift-corelibs-dev] Need of inputs for NSExpression
> 
> Hi Nethra,
> 
> Thanks for your interest!
> 
> Probably the best place to get started would be to take a look at our 
> documentation about NSExpression. Some of it is pretty tricky to implement 
> without the dynamic behavior of ObjC though.
> 
> - Tony
> 
>> On Jan 12, 2017, at 4:24 AM, Nethra Ravindran via swift-corelibs-dev 
>> > wrote:
>> 
>> Hi All,
>> 
>> This is Nethra Ravindran and I’m a university student doing my internship. I 
>> would like to contribute to Swift Foundation. I have looked upon 
>> NSExpression and I am interested in contributing the implementation. I would 
>> be very thankful if I could get some pointers about it.
>> 
>> Thank you in advance for your help!
>> 
>> Regards,
>> Nethra Ravindran
>> 
>> ___
>> 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 
> 
> 

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

Re: [swift-corelibs-dev] [swift-build-dev] Final merge from master to swift-3.1-branch

[Tony Parker via swift-corelibs-dev]

Thanks Mishal!

For all of the contributors to swift-corelibs: if you have a change which you 
think is appropriate for inclusion into Swift 3.1, let’s follow this process:

1. Get a PR up for master to merge your change
2. Once accepted, get a PR up to cherry pick the change to the swift-3.1 
branch. We can have a discussion there about if it’s appropriate for swift 3.1, 
or we can chat about it on the mailing list first if you like.

For Swift 3.1 changes, let’s focus on:

* Regressions from Swift 3.0
* Critical work for server side Swift

New work for unimplemented API can continue on master for the next Swift 
release.

Thanks!

- Tony

> On Jan 17, 2017, at 2:33 PM, mishal_shah via swift-corelibs-dev 
>  wrote:
> 
> I just merged master into swift-3.1-branch for following projects. 
> 
> https://github.com/apple/swift 
> https://github.com/apple/swift-lldb 
> https://github.com/apple/swift-corelibs-foundation 
> 
> https://github.com/apple/swift-corelibs-libdispatch 
> 
> https://github.com/apple/swift-corelibs-xctest 
> 
> https://github.com/apple/swift-integration-tests 
> 
> https://github.com/apple/swift-xcode-playground-support 
> 
> https://github.com/apple/swift-package-manager 
> 
> https://github.com/apple/swift-llbuild 
> 
> 
> Thanks, 
> Mishal Shah
>> On Jan 13, 2017, at 6:49 AM, Nicole Jacque via swift-build-dev 
>> > wrote:
>> 
>> Hello Swift Developers-
>> 
>> As outlined in Ted’s Swift 3.1 Release Process blog post, for the past 
>> month, we’ve been periodically merging master to the swift-3.1-branch 
>> branch.  We will be doing one final merge of master to the swift-3.1-branch 
>> on January 17 at noon (Pacific). Note that we’ve pushed this back a day due 
>> to the MLK Jr. Day holiday.   Any changes landed after that time will 
>> require approval via a pull request against the swift-3.1-branch branch in 
>> order to include them in the Swift 3.1 release.  After this final merge, 
>> development on master will be targeted for Swift 4.
>> 
>> Snapshots of the swift-3.1-branch will be made available on the downloads 
>> page (https://swift.org/download/ ).  Snapshots 
>> will be made available daily, if all package generation CI tests are passing.
>> ___
>> swift-build-dev mailing list
>> swift-build-...@swift.org 
>> https://lists.swift.org/mailman/listinfo/swift-build-dev
> 
> ___
> 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