The question is the subject, but anyway I’ll repeat it here: Why URL
doesn't have fileReferenceURL and isFileReferenceURL, but NSURL has? Is
it by design? If it’s a bug I can create an issue in https://bugs.swift.org.
It seems this is intentional, see SR-2728:
https://bugs.swift.org/browse/SR-2
The main reason is actually that we just prefer people use
NSPropertyListSerialization API to read or write property lists. One big
reason: that API has the possibility of giving you an error, whereas the
collection methods do not.
Thanks for the quick reply, Tony, that makes sense. I also hadn'
(Apologies if this is not the right list to ask this question. I couldn't
decide between swift-corelibs-dev and swift-dev.)
I noticed that the NSArray and NSDictionary initializers to create a collection
from a property list file are not exposed in the stdlib Array and Dictionary
types. The sam
