[swift-evolution] [Pitch] String revision proposal #1

[Karim Nassar]

> Message: 12
> Date: Thu, 30 Mar 2017 12:23:13 +0200
> From: Adrian Zubarev <adrian.zubarev at devandartist.com>
> To: Ben Cohen <ben_cohen at apple.com>
> Cc: swift-evolution at swift.org
> Subject: Re: [swift-evolution] [Pitch] String revision proposal #1
> Message-ID: <etPan.58dcdc91.583a4c4b.1af7 at devandartist.com>
> Content-Type: text/plain; charset="utf-8"
> 
> I haven’t followed the topic and while reading the proposal I found it a little confusing that we have inconsistent type names. I’m not a native English speaker so that’s might be the main case for my confusion here, so I’d appreciate for any clarification. ;-)
> 
> SubSequence vs. Substring and not SubString.
> 
> The word substring is an English word, but so is subsequence (I double checked here).
> 
> So where exactly is the issue here? Is it SubSequence which is written in camel case or is it Substring which is not?
> 
> 
> 
> -- 
> Adrian Zubarev
> Sent with Airmail


I’d also be curious if StringSlice was considered, since we have already the well-established and seemingly-parallel ArraySlice.

—Karim