Now that I see it, I realise I’ve run in to that a fair few times myself; I
didn’t even know the string-view initialisers were failable.
I’m not sure I understand why reflection is exposed as an initialiser on String
in the first place - it might make more sense as a global function.
Karl
> On
On May 9, 2016, at 10:25 AM, Joe Groff via swift-users
wrote:
>> This seems like a tricky gotcha for developers who aren't extremely familiar
>> with both the String and reflection APIs. His code looked reasonable at a
>> first glance and I didn't suspect anything was wrong until I profiled it.
Thanks to all who commented. I'll put together a proposal to rename that
initializer tonight, unless someone else wants to do it. This seems like a
pretty straightforward clarity gain, and it might even help a bit with
compilation times.
Austin
On Mon, May 9, 2016 at 10:54 AM, Daniel Dunbar via s
> On May 9, 2016, at 10:28 AM, Jacob Bandes-Storch via swift-users
> wrote:
>
> On Mon, May 9, 2016 at 10:25 AM, Joe Groff via swift-users
> mailto:swift-users@swift.org>> wrote:
>
> > On May 7, 2016, at 10:39 AM, Austin Zheng via swift-users
> > mailto:swift-users@swift.org>> wrote:
> >
> >
On Mon, May 9, 2016 at 10:25 AM, Joe Groff via swift-users <
swift-users@swift.org> wrote:
>
> > On May 7, 2016, at 10:39 AM, Austin Zheng via swift-users <
> swift-users@swift.org> wrote:
> >
> > Hello Swift users,
> >
> > I wanted to run something past you folks and get some opinions/feedback.
>
On Mon, May 9, 2016, at 01:25 PM, Joe Groff via swift-users wrote:
> This definitely strikes me as a problem. The String(_:) constructor is
> very easy to call by accident if you're trying to hit another unlabeled
> initializer. It also strikes me as not particularly "value-preserving",
> since str
> On May 7, 2016, at 10:39 AM, Austin Zheng via swift-users
> wrote:
>
> Hello Swift users,
>
> I wanted to run something past you folks and get some opinions/feedback.
>
> About a month ago on Hacker News I saw someone commenting about how Swift's
> string-handling code was unbearably slow
Hi Austin,
I further “swiftyfied” the code to this
(swift-DEVELOPMENT-SNAPSHOT-2016-05-03-a):
import Foundation
let N = 1_000_000
func generateTestData() -> [String] {
return (0.. [String] {
return s.characters.split(separator: sep, omittingEmptySubsequences: false)
.m
Hello Swift users,
I wanted to run something past you folks and get some opinions/feedback.
About a month ago on Hacker News I saw someone commenting about how Swift's
string-handling code was unbearably slow (3 seconds to run a code sample, vs.
0.8 in Java). I asked him to provide the code, an
