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
> 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
> > wrote:
>
> > On May 7, 2016, at 10:39 AM, Austin Zheng via swift-users
>
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
> 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
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..
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,