Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Dave Abrahams via swift-evolution]

on Wed Sep 28 2016, Erica Sadun  wrote:

> Chris: "Also, it is worth saying that any source breaking change still has to 
> have an 
> ultra-compelling reason to be worth considering.  Despite having a framework 
> to 
> support some source breaking changes, we still want to minimize them where 
> ever possible."
>
> Since it seems to be open season on introducing a few, highly focused
> breaking changes, let me throw this one out there.
>
> Pitch: Renaming CharacterSet to UnicodeScalarSet

Hi Erica,

This is out-of-scope for this list, because CharacterSet is part of
corelibs-foundation.  I suggest posting on
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev, where the
Foundation people hang.

> In Swift, String is defined as "a Unicode string value." and a "CharacterSet" 
> represents a set of Unicode-compliant characters.
>
> A CharacterSet's initializers are:
> init()
> init(S)
> init(arrayLiteral: UnicodeScalar...)
> init(bitmapRepresentation: Data)
> init(charactersIn: ClosedRange)
> init(charactersIn: String)
> init(charactersIn: Range)
> init?(contentsOfFile: String)
>
> Why not rename `CharacterSet` to `UnicodeScalarSe`t, and update the 
> initializers
> to reflect they're being initialized from the unicode scalars in strings and 
> ranges?
> I think the few places where the word `character` is left mentioned (in 
> convenience
> properties) can be better named from `punctuationCharacters` to 
> `punctuation`, 
> `controlCharacters` to `controlAndFormat`, etc.
>
> -- E
> ___
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>

-- 
-Dave

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

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[David Sweeris via swift-evolution]

IIUC, Jay wasn't arguing for renaming CharacterSet, but replacing it with 
Swift's existing Set mechanism. If/when generics get to the point that we can 
say 'extension Set {...}', I think the transition could simply be 
putting 'typealias CharacterSet = Set' somewhere in the framework 
(although I don't know how Obj-C interop would be affected by such a change).

- Dave Sweeris

> On Sep 29, 2016, at 00:30, Xiaodi Wu via swift-evolution 
>  wrote:
> 
> CharacterSet is a Foundation value type. It was a subject of the following 
> proposal:
> 
> https://github.com/apple/swift-evolution/blob/master/proposals/0069-swift-mutability-for-foundation.md
> 
> We might be able improve on the implementation, but I don't think re-arguing 
> the name is an option.
> 
> 
>> On Wed, Sep 28, 2016 at 11:59 PM Jay Abbott  wrote:
>> 
>> Yes - this is totally confusing. CharacterSet and Set are 
>> completely different things with different semantics.
>> 
>> I don't know the history, but is CharacterSet simply to have a Swift 
>> equivalent of NSCharacterSet? That seems to be what it is, but since Swift 
>> redefined characters in a better way, this should be removed or called 
>> something else to avoid confusion. You shouldn't have to qualify what you 
>> mean by 'character' in a type name because it diverges from the definition 
>> in the rest of the language.
>> 
>>> On Thu, 29 Sep 2016 at 04:48 Xiaodi Wu via swift-evolution 
>>>  wrote:
 On Wed, Sep 28, 2016 at 10:34 PM, Xiaodi Wu  wrote:
>>> 
 On Wed, Sep 28, 2016 at 10:23 PM, Charles Srstka via swift-evolution 
  wrote:
>> On Sep 28, 2016, at 9:57 PM, Erica Sadun via swift-evolution 
>>  wrote:
>> 
>> D'erp. I missed that. And that's an unambiguous answer.
>> 
>> So let me move on to part B of the pitch: I think CharacterSets are 
>> broken.
>> 
>>> Xiaodi Wu: "isn't the problem you're presenting really an argument that 
>>> the type should be fleshed out to handle characters (grapheme clusters) 
>>> containing more than one Unicode scalar?"
> 
> It seems that it already does handle such characters:
> 
> (done in Objective-C so we can log the length of the range as a count of 
> UTF-16 code units)
> 
> #import 
> 
> int main(int argc, char *argv[]) {
> @autoreleasepool {
> NSCharacterSet *bikeSet = [NSCharacterSet 
> characterSetWithCharactersInString:@"🚲"];
> NSString *str = @"foo🚲bar";
> 
> NSRange range = [str rangeOfCharacterFromSet:bikeSet];
> 
> NSLog(@"location: %lu length: %lu", range.location, range.length);
> }
> }
> 
> - - - - - - -
> 
> 2016-09-28 22:20:00.622471 test[15577:2433912] location: 3 length: 2
> Program ended with exit code: 0
> 
> - - - - - - -
> 
> As we can see, the character from the set is recognized as consisting of 
> two code units. There are a few bugs in the system, though. See the 
> cocoa-dev thread “Where is my bicycle?” from about a year ago: 
> http://prod.lists.apple.com/archives/cocoa-dev/2015/Apr/msg00074.html
 
 The bike emoji might be two code units, but it is one Unicode scalar 
 (U+1F6B2). However, the Canadian flag emoji, for instance, is two Unicode 
 scalars (U+1F1E8 U+1F1E6) but nonetheless one character.
>>> 
>>> To illustrate in code how CharacterSet doesn't actually handle characters 
>>> made up of multiple Unicode scalars:
>>> 
>>> ```
>>> import Foundation
>>> 
>>> let str1 = "🇦🇩"
>>> let first = CharacterSet(charactersIn: str1) // this actually crashes 
>>> corelibs-foundation
>>> let str2 = "🇦🇺"
>>> let second = CharacterSet(charactersIn: str2)
>>> let intersection = first.intersection(second)
>>> print(intersection.isEmpty)
>>> // actual output: false
>>> // obviously, if we were really dealing with characters, the intersection 
>>> should be empty
>>> ```
>>> 
 
> Charles
> 
> 
> ___
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
> 
 
>>> ___
>>> swift-evolution mailing list
>>> swift-evolution@swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-evolution
> ___
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
___
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Xiaodi Wu via swift-evolution]

CharacterSet is a Foundation value type. It was a subject of the following
proposal:

https://github.com/apple/swift-evolution/blob/master/proposals/0069-swift-mutability-for-foundation.md

We might be able improve on the implementation, but I don't think
re-arguing the name is an option.


On Wed, Sep 28, 2016 at 11:59 PM Jay Abbott  wrote:

>
> Yes - this is totally confusing. CharacterSet and Set are
> completely different things with different semantics.
>
> I don't know the history, but is CharacterSet simply to have a Swift
> equivalent of NSCharacterSet? That seems to be what it is, but since Swift
> redefined characters in a better way, this should be removed or called
> something else to avoid confusion. You shouldn't have to qualify what you
> mean by 'character' in a type name because it diverges from the definition
> in the rest of the language.
>
> On Thu, 29 Sep 2016 at 04:48 Xiaodi Wu via swift-evolution <
> swift-evolution@swift.org> wrote:
>
>> On Wed, Sep 28, 2016 at 10:34 PM, Xiaodi Wu  wrote:
>>
>>> On Wed, Sep 28, 2016 at 10:23 PM, Charles Srstka via swift-evolution <
>>> swift-evolution@swift.org> wrote:
>>>
 On Sep 28, 2016, at 9:57 PM, Erica Sadun via swift-evolution <
 swift-evolution@swift.org> wrote:


 D'erp. I missed that. And that's an unambiguous answer.

 So let me move on to part B of the pitch: I think CharacterSets are
 broken.

 Xiaodi Wu: "isn't the problem you're presenting really an argument that
 the type should be fleshed out to handle characters (grapheme clusters)
 containing more than one Unicode scalar?"


 It seems that it already does handle such characters:

 (done in Objective-C so we can log the length of the range as a count
 of UTF-16 code units)

 #import 

 int main(int argc, char *argv[]) {
 @autoreleasepool {
 NSCharacterSet *bikeSet = [NSCharacterSet
 characterSetWithCharactersInString:@"🚲"];
 NSString *str = @"foo🚲bar";


 NSRange range = [str rangeOfCharacterFromSet:bikeSet];


 NSLog(@"location: %lu length: %lu", range.location, range.
 length);
 }
 }

 - - - - - - -

 *2016-09-28 22:20:00.622471 test[15577:2433912] location: 3 length: 2*
 *Program ended with exit code: 0*

 - - - - - - -

 As we can see, the character from the set is recognized as consisting
 of two code units. There are a few bugs in the system, though. See the
 cocoa-dev thread “Where is my bicycle?” from about a year ago:
 http://prod.lists.apple.com/archives/cocoa-dev/2015/Apr/msg00074.html

>>>
>>> The bike emoji might be two code units, but it is one Unicode scalar
>>> (U+1F6B2). However, the Canadian flag emoji, for instance, is two Unicode
>>> scalars (U+1F1E8 U+1F1E6) but nonetheless one character.
>>>
>>
>> To illustrate in code how CharacterSet doesn't actually handle characters
>> made up of multiple Unicode scalars:
>>
>> ```
>> import Foundation
>>
>> let str1 = "🇦🇩"
>> let first = CharacterSet(charactersIn: str1) // this actually crashes
>> corelibs-foundation
>> let str2 = "🇦🇺"
>> let second = CharacterSet(charactersIn: str2)
>> let intersection = first.intersection(second)
>> print(intersection.isEmpty)
>> // actual output: false
>> // obviously, if we were really dealing with characters, the intersection
>> should be empty
>> ```
>>
>>
>>> Charles


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


>>> ___
>> swift-evolution mailing list
>> swift-evolution@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>
>
___
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Jay Abbott via swift-evolution]

Yes - this is totally confusing. CharacterSet and Set are
completely different things with different semantics.

I don't know the history, but is CharacterSet simply to have a Swift
equivalent of NSCharacterSet? That seems to be what it is, but since Swift
redefined characters in a better way, this should be removed or called
something else to avoid confusion. You shouldn't have to qualify what you
mean by 'character' in a type name because it diverges from the definition
in the rest of the language.

On Thu, 29 Sep 2016 at 04:48 Xiaodi Wu via swift-evolution <
swift-evolution@swift.org> wrote:

> On Wed, Sep 28, 2016 at 10:34 PM, Xiaodi Wu  wrote:
>
>> On Wed, Sep 28, 2016 at 10:23 PM, Charles Srstka via swift-evolution <
>> swift-evolution@swift.org> wrote:
>>
>>> On Sep 28, 2016, at 9:57 PM, Erica Sadun via swift-evolution <
>>> swift-evolution@swift.org> wrote:
>>>
>>>
>>> D'erp. I missed that. And that's an unambiguous answer.
>>>
>>> So let me move on to part B of the pitch: I think CharacterSets are
>>> broken.
>>>
>>> Xiaodi Wu: "isn't the problem you're presenting really an argument that
>>> the type should be fleshed out to handle characters (grapheme clusters)
>>> containing more than one Unicode scalar?"
>>>
>>>
>>> It seems that it already does handle such characters:
>>>
>>> (done in Objective-C so we can log the length of the range as a count of
>>> UTF-16 code units)
>>>
>>> #import 
>>>
>>> int main(int argc, char *argv[]) {
>>> @autoreleasepool {
>>> NSCharacterSet *bikeSet = [NSCharacterSet
>>> characterSetWithCharactersInString:@"🚲"];
>>> NSString *str = @"foo🚲bar";
>>>
>>>
>>> NSRange range = [str rangeOfCharacterFromSet:bikeSet];
>>>
>>>
>>> NSLog(@"location: %lu length: %lu", range.location, range.length
>>> );
>>> }
>>> }
>>>
>>> - - - - - - -
>>>
>>> *2016-09-28 22:20:00.622471 test[15577:2433912] location: 3 length: 2*
>>> *Program ended with exit code: 0*
>>>
>>> - - - - - - -
>>>
>>> As we can see, the character from the set is recognized as consisting of
>>> two code units. There are a few bugs in the system, though. See the
>>> cocoa-dev thread “Where is my bicycle?” from about a year ago:
>>> http://prod.lists.apple.com/archives/cocoa-dev/2015/Apr/msg00074.html
>>>
>>
>> The bike emoji might be two code units, but it is one Unicode scalar
>> (U+1F6B2). However, the Canadian flag emoji, for instance, is two Unicode
>> scalars (U+1F1E8 U+1F1E6) but nonetheless one character.
>>
>
> To illustrate in code how CharacterSet doesn't actually handle characters
> made up of multiple Unicode scalars:
>
> ```
> import Foundation
>
> let str1 = "🇦🇩"
> let first = CharacterSet(charactersIn: str1) // this actually crashes
> corelibs-foundation
> let str2 = "🇦🇺"
> let second = CharacterSet(charactersIn: str2)
> let intersection = first.intersection(second)
> print(intersection.isEmpty)
> // actual output: false
> // obviously, if we were really dealing with characters, the intersection
> should be empty
> ```
>
>
>> Charles
>>>
>>>
>>> ___
>>> swift-evolution mailing list
>>> swift-evolution@swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>>
>>>
>> ___
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
___
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Xiaodi Wu via swift-evolution]

On Wed, Sep 28, 2016 at 10:34 PM, Xiaodi Wu  wrote:

> On Wed, Sep 28, 2016 at 10:23 PM, Charles Srstka via swift-evolution <
> swift-evolution@swift.org> wrote:
>
>> On Sep 28, 2016, at 9:57 PM, Erica Sadun via swift-evolution <
>> swift-evolution@swift.org> wrote:
>>
>>
>> D'erp. I missed that. And that's an unambiguous answer.
>>
>> So let me move on to part B of the pitch: I think CharacterSets are
>> broken.
>>
>> Xiaodi Wu: "isn't the problem you're presenting really an argument that
>> the type should be fleshed out to handle characters (grapheme clusters)
>> containing more than one Unicode scalar?"
>>
>>
>> It seems that it already does handle such characters:
>>
>> (done in Objective-C so we can log the length of the range as a count of
>> UTF-16 code units)
>>
>> #import 
>>
>> int main(int argc, char *argv[]) {
>> @autoreleasepool {
>> NSCharacterSet *bikeSet = [NSCharacterSet
>> characterSetWithCharactersInString:@"🚲"];
>> NSString *str = @"foo🚲bar";
>>
>>
>> NSRange range = [str rangeOfCharacterFromSet:bikeSet];
>>
>>
>> NSLog(@"location: %lu length: %lu", range.location, range.length
>> );
>> }
>> }
>>
>> - - - - - - -
>>
>> *2016-09-28 22:20:00.622471 test[15577:2433912] location: 3 length: 2*
>> *Program ended with exit code: 0*
>>
>> - - - - - - -
>>
>> As we can see, the character from the set is recognized as consisting of
>> two code units. There are a few bugs in the system, though. See the
>> cocoa-dev thread “Where is my bicycle?” from about a year ago:
>> http://prod.lists.apple.com/archives/cocoa-dev/2015/Apr/msg00074.html
>>
>
> The bike emoji might be two code units, but it is one Unicode scalar
> (U+1F6B2). However, the Canadian flag emoji, for instance, is two Unicode
> scalars (U+1F1E8 U+1F1E6) but nonetheless one character.
>

To illustrate in code how CharacterSet doesn't actually handle characters
made up of multiple Unicode scalars:

```
import Foundation

let str1 = "🇦🇩"
let first = CharacterSet(charactersIn: str1) // this actually crashes
corelibs-foundation
let str2 = "🇦🇺"
let second = CharacterSet(charactersIn: str2)
let intersection = first.intersection(second)
print(intersection.isEmpty)
// actual output: false
// obviously, if we were really dealing with characters, the intersection
should be empty
```


> Charles
>>
>>
>> ___
>> swift-evolution mailing list
>> swift-evolution@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>
>>
>
___
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Xiaodi Wu via swift-evolution]

On Wed, Sep 28, 2016 at 10:23 PM, Charles Srstka via swift-evolution <
swift-evolution@swift.org> wrote:

> On Sep 28, 2016, at 9:57 PM, Erica Sadun via swift-evolution <
> swift-evolution@swift.org> wrote:
>
>
> D'erp. I missed that. And that's an unambiguous answer.
>
> So let me move on to part B of the pitch: I think CharacterSets are broken.
>
> Xiaodi Wu: "isn't the problem you're presenting really an argument that
> the type should be fleshed out to handle characters (grapheme clusters)
> containing more than one Unicode scalar?"
>
>
> It seems that it already does handle such characters:
>
> (done in Objective-C so we can log the length of the range as a count of
> UTF-16 code units)
>
> #import 
>
> int main(int argc, char *argv[]) {
> @autoreleasepool {
> NSCharacterSet *bikeSet = [NSCharacterSet
> characterSetWithCharactersInString:@"🚲"];
> NSString *str = @"foo🚲bar";
>
>
> NSRange range = [str rangeOfCharacterFromSet:bikeSet];
>
>
> NSLog(@"location: %lu length: %lu", range.location, range.length);
> }
> }
>
> - - - - - - -
>
> *2016-09-28 22:20:00.622471 test[15577:2433912] location: 3 length: 2*
> *Program ended with exit code: 0*
>
> - - - - - - -
>
> As we can see, the character from the set is recognized as consisting of
> two code units. There are a few bugs in the system, though. See the
> cocoa-dev thread “Where is my bicycle?” from about a year ago:
> http://prod.lists.apple.com/archives/cocoa-dev/2015/Apr/msg00074.html
>

The bike emoji might be two code units, but it is one Unicode scalar
(U+1F6B2). However, the Canadian flag emoji, for instance, is two Unicode
scalars (U+1F1E8 U+1F1E6) but nonetheless one character.

Charles
>
>
> ___
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
___
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Charles Srstka via swift-evolution]

> On Sep 28, 2016, at 9:57 PM, Erica Sadun via swift-evolution 
>  wrote:
> 
> D'erp. I missed that. And that's an unambiguous answer.
> 
> So let me move on to part B of the pitch: I think CharacterSets are broken.
> 
>> Xiaodi Wu: "isn't the problem you're presenting really an argument that the 
>> type should be fleshed out to handle characters (grapheme clusters) 
>> containing more than one Unicode scalar?"

It seems that it already does handle such characters:

(done in Objective-C so we can log the length of the range as a count of UTF-16 
code units)

#import 

int main(int argc, char *argv[]) {
@autoreleasepool {
NSCharacterSet *bikeSet = [NSCharacterSet 
characterSetWithCharactersInString:@"🚲"];
NSString *str = @"foo🚲bar";

NSRange range = [str rangeOfCharacterFromSet:bikeSet];

NSLog(@"location: %lu length: %lu", range.location, range.length);
}
}

- - - - - - -

2016-09-28 22:20:00.622471 test[15577:2433912] location: 3 length: 2
Program ended with exit code: 0

- - - - - - -

As we can see, the character from the set is recognized as consisting of two 
code units. There are a few bugs in the system, though. See the cocoa-dev 
thread “Where is my bicycle?” from about a year ago: 
http://prod.lists.apple.com/archives/cocoa-dev/2015/Apr/msg00074.html 


Charles

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

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Erica Sadun via swift-evolution]

On Sep 28, 2016, at 6:14 PM, Ben Rimmington  wrote:
> 
> 
>> On 28 Sep 2016, at 22:27, Erica Sadun wrote:
>> 
>> Why not rename `CharacterSet` to `UnicodeScalarSe`t, and update the 
>> initializers
>> to reflect they're being initialized from the unicode scalars in strings and 
>> ranges?
> 
> I agree, but `UnicodeScalarSet` was rejected during the SE-0069 discussion:
> 
> 
> 
> -- Ben
> 

D'erp. I missed that. And that's an unambiguous answer.

So let me move on to part B of the pitch: I think CharacterSets are broken.

> Xiaodi Wu: "isn't the problem you're presenting really an argument that the 
> type should be fleshed out to handle characters (grapheme clusters) 
> containing more than one Unicode scalar?"

-- E
___
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Ben Rimmington via swift-evolution]

> On 28 Sep 2016, at 22:27, Erica Sadun wrote:
> 
> Why not rename `CharacterSet` to `UnicodeScalarSe`t, and update the 
> initializers
> to reflect they're being initialized from the unicode scalars in strings and 
> ranges?

I agree, but `UnicodeScalarSet` was rejected during the SE-0069 discussion:



-- Ben

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

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Xiaodi Wu via swift-evolution]

Afaik, every Unicode scalar can be its own character, so IMO it's not
bothersome that there are overloads that take Unicode scalar arguments.
However, since the stated purpose of the type is to be a set of characters,
isn't the problem you're presenting really an argument that the type should
be fleshed out to handle characters (grapheme clusters) containing more
than one Unicode scalar?


On Wed, Sep 28, 2016 at 18:43 Erica Sadun  wrote:

> On Sep 28, 2016, at 3:58 PM, Xiaodi Wu  wrote:
>
>
> Is this really correct? Character and UnicodeScalar are not synonyms. The
> Character type represents a character made up of one or more Unicode
> scalars (i.e. an extended grapheme cluster). Is a CharacterSet a set of
> Unicode-compliant characters that happens to be restricted to those
> characters each made up of only a single Unicode scalar, or is it meant to
> be a set of Unicode scalars? My read of the Foundation documentation is
> that it is the former.
>
>
> http://i.imgur.com/h6W5kYc.jpg
>
> http://i.imgur.com/q50PSld.jpg
>
> -- E
>
>
>
___
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Erica Sadun via swift-evolution]

On Sep 28, 2016, at 3:58 PM, Xiaodi Wu  wrote:
> 
> Is this really correct? Character and UnicodeScalar are not synonyms. The 
> Character type represents a character made up of one or more Unicode scalars 
> (i.e. an extended grapheme cluster). Is a CharacterSet a set of 
> Unicode-compliant characters that happens to be restricted to those 
> characters each made up of only a single Unicode scalar, or is it meant to be 
> a set of Unicode scalars? My read of the Foundation documentation is that it 
> is the former.

http://i.imgur.com/h6W5kYc.jpg 

http://i.imgur.com/q50PSld.jpg 

-- E


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

Re: [swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Xiaodi Wu via swift-evolution]

Is this really correct? Character and UnicodeScalar are not synonyms. The
Character type represents a character made up of one or more Unicode
scalars (i.e. an extended grapheme cluster). Is a CharacterSet a set of
Unicode-compliant characters that happens to be restricted to those
characters each made up of only a single Unicode scalar, or is it meant to
be a set of Unicode scalars? My read of the Foundation documentation is
that it is the former.


On Wed, Sep 28, 2016 at 4:27 PM, Erica Sadun via swift-evolution <
swift-evolution@swift.org> wrote:

> Chris: "*Also, it is worth saying that any source breaking change still
> has to have an *
> *ultra-compelling reason to be worth considering.  Despite having a
> framework to *
> *support some source breaking changes, we still want to minimize them
> where *
> *ever possible.*"
>
> Since it seems to be open season on introducing a few, highly focused
> breaking changes, let me throw this one out there.
>
> *Pitch: Renaming CharacterSet to UnicodeScalarSet*
>
> In Swift, String is defined as "a Unicode string value." and a
> "CharacterSet"
> represents a set of Unicode-compliant characters.
>
> A CharacterSet's initializers are:
>
>- init()
>- init(S)
>- init(arrayLiteral: UnicodeScalar...)
>- init(bitmapRepresentation: Data)
>- init(charactersIn: ClosedRange)
>- init(charactersIn: String)
>- init(charactersIn: Range)
>- init?(contentsOfFile: String)
>
>
> Why not rename `CharacterSet` to `UnicodeScalarSe`t, and update the
> initializers
> to reflect they're being initialized from the unicode scalars in strings
> and ranges?
> I think the few places where the word `character` is left mentioned (in
> convenience
> properties) can be better named from `punctuationCharacters` to
> `punctuation`,
> `controlCharacters` to `controlAndFormat`, etc.
>
> -- E
>
> ___
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
___
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

[swift-evolution] Pitch: Renaming CharacterSet to UnicodeScalarSet

[Erica Sadun via swift-evolution]

Chris: "Also, it is worth saying that any source breaking change still has to 
have an 
ultra-compelling reason to be worth considering.  Despite having a framework to 
support some source breaking changes, we still want to minimize them where 
ever possible."

Since it seems to be open season on introducing a few, highly focused
breaking changes, let me throw this one out there.

Pitch: Renaming CharacterSet to UnicodeScalarSet

In Swift, String is defined as "a Unicode string value." and a "CharacterSet" 
represents a set of Unicode-compliant characters.

A CharacterSet's initializers are:
init()
init(S)
init(arrayLiteral: UnicodeScalar...)
init(bitmapRepresentation: Data)
init(charactersIn: ClosedRange)
init(charactersIn: String)
init(charactersIn: Range)
init?(contentsOfFile: String)

Why not rename `CharacterSet` to `UnicodeScalarSe`t, and update the initializers
to reflect they're being initialized from the unicode scalars in strings and 
ranges?
I think the few places where the word `character` is left mentioned (in 
convenience
properties) can be better named from `punctuationCharacters` to `punctuation`, 
`controlCharacters` to `controlAndFormat`, etc.

-- E___
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution