[swift-corelibs-dev] NSKeyValueCoding and the Swift Foundation

[Lars Sonchocky-Helldorf via swift-corelibs-dev]

Hi everybody,

it came to my attention that the NSKeyValueCoding protocol which is a part of 
the Darwin-(ObjC-)Foundation (see 
https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Protocols/NSKeyValueCoding_Protocol/
 ) is somehow omitted here: 
https://github.com/apple/swift-corelibs-foundation/blob/master/Docs/Status.md

Was this done on purpose or is the implementation of NSKeyValueCoding still 
forthcoming?

Thanks,

Lars


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

Re: [swift-corelibs-dev] NSKeyValueCoding and the Swift Foundation

[Lars Sonchocky-Helldorf via swift-corelibs-dev]

To my understanding the real reason why this is currently not possible is 
rooted in the limitations of struct Mirror, which, for instance, lacks the 
support for writing and the reflection of methods.

So it boils down to the following: Are there currently any plans to extend the 
capabilities of struct Mirror to support better reflection?


Trying to answer this question I found this post: 

https://lists.swift.org/pipermail/swift-users/Week-of-Mon-20151214/000512.html

where Joe Groff says there is something planned.


Are there any news on this, maybe a rough timeframe or Swift version for which 
to expect better reflection support?


Thanks,

Lars

> Am 12.06.2016 um 20:40 schrieb Philippe Hausler :
> 
> Both KVC and KVO require dynamic dispatching and selector manipulation that 
> is not present in swift-corelibs-foundation (since everything is based on 
> swift objects).
> 
>> On Jun 12, 2016, at 10:54 AM, Lars Sonchocky-Helldorf via swift-corelibs-dev 
>>  wrote:
>> 
>> Hi everybody,
>> 
>> it came to my attention that the NSKeyValueCoding protocol which is a part 
>> of the Darwin-(ObjC-)Foundation (see 
>> https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Protocols/NSKeyValueCoding_Protocol/
>>  ) is somehow omitted here: 
>> https://github.com/apple/swift-corelibs-foundation/blob/master/Docs/Status.md
>> 
>> Was this done on purpose or is the implementation of NSKeyValueCoding still 
>> forthcoming?
>> 
>> Thanks,
>> 
>>  Lars
>> 
>> 
>> ___
>> 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] Discourse rollout re-schedule

[Lars Sonchocky-Helldorf via swift-corelibs-dev]

Hi Nicole,

> Am 15.12.2017 um 03:59 schrieb Nicole Jacque via swift-corelibs-dev 
> :
> 
> Hi All-
> 
> First of all, a big thank you to everyone who has provided feedback on our 
> prototype Discourse forum.  Based on the fact that we’re still receiving 
> feedback, we’d like to move to a slightly less aggressive schedule for our 
> rollout, in order to make sure that we’ve adequately addressed it.  We’re 
> still working out an exact schedule, but due to the upcoming holidays, I 
> expect that we’ll be looking at shortly after the beginning of the new year.
> 
> In the meantime, I’ve moved the prototype forum to https://forums.swift.org, 
> and I have GitHub-enabled logins working if you’d like to give it a try!  You 
> can also test out registering (including using the staged account pre-created 
> from your mailing list account).  Instructions are here: 
> https://forums.swift.org/t/taking-over-a-pre-created-staged-account/7121 
> 

that link doesn’t work for me, it redirects me to:

https://forums.swift.org/t/synthesizing-equatable-hashable-and-comparable-for-tuple-types/7121
 


I am missing something?

Thanks and happy new year,

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