> Sorry, I said NSProgress but I meant NSPredicate. I personally can't even
> imagine what a alternative API for NSPredicate would look like 🤔
Use reflection.
Match against only dictionaries with string keys.
Match against only objects conforming to some dictionary-with-string-keys-like
protoc
What code will be used to make then _localized_?
/Daniel
> On 17 Mar 2016, at 19:15, Ian Partridge via swift-corelibs-dev
> wrote:
>
> Hi Philippe, thanks for your quick reply.
>
> The HTTP status code reason phrases are designed to be human readable.
> They are standard phrases that are easi
Sorry for intruding!I have the same question about /*@NSCopying*/ Â Pushkar N Kulkarni,
IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra
-swift-corelibs-dev-boun...@swift.org wrote: -To: Daniel Eggert From: Philippe Hausler via swift-corelibs-d
I created https://github.com/apple/swift-corelibs-foundation/pull/290
to add 4 attributes that were missing compared to Darwin Foundation.
I also re-worked how attributes are used / stored for the immutable / mutable
version.
I didn't add any documentation to the 4 attributes, because I didn't k
That is a comment emitted by the importer, unfortunately it is impossible for
non objc to mimic that behavior 100% because it is an init method that is
constructed from a class method.
@interface Foo : NSObject
+ (Foo *)fooNamed:(NSString *)name; // this is not an inherited init method in
that
There're some initializers (namely in NSURLSession) that have a comment:
public /*not inherited*/ init(...
What is this “not inherited” comment trying to convey, and how would one go
about implementing this in Swift?
/Daniel
___
swift-corelibs-dev ma
Awesome, thanks for taking this on!
- Tony
> On Mar 17, 2016, at 12:33 PM, Daniel Eggert via swift-corelibs-dev
> wrote:
>
> I’ve made good progress on this. I’ll try to get something that’s merge-able
> within the next week. It won’t be 100% complete by any means, but should
> hopefully (A)
Hi,
A quick question about implementing this method.
Do we want the strings returned to match those returned by the
Objective-C implementation of Foundation, or follow RFC 2616?
Currently they are inconsistent, e.g. Obj-C Foundation returns "no
error" for status code 200, whereas the RFC says thi
I am trying to implement some of the methods and properties in NSOrderedSet. The read-only property "reversedOrderedSet" has the @NSCopying attribute according to the NSOrderedSet class reference. So, I tried to do this: @NSCopying public var reversedOrderedSet: NSOrderedSet {   return NSOrderedSe
I personally find inline documentation helpful as a reminder of the goal of
the desired behavior.
Sent from my iPhone
> On Mar 16, 2016, at 7:47 AM, Daniel Eggert via swift-corelibs-dev
> wrote:
>
> I created https://github.com/apple/swift-corelibs-foundation/pull/290
> to add 4 attributes t
Hi Philippe, thanks for your quick reply.
The HTTP status code reason phrases are designed to be human readable.
They are standard phrases that are easily searched for online.
The latest table is at
http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml
- isn't there a case for
On 17 Mar 2016, at 19:52, Ian Partridge via swift-corelibs-dev
wrote:
> I wondered if Obj-C foundation translated them based
> on the current locale, but it doesn't.
It should translate them based on the current language (not locale). The fact
that it doesn't is a bug. This seems to be yet
12 matches
Mail list logo