Re: [swift-users] Store objects of generic types in a data structure

2017-04-08 Thread Brent Royal-Gordon via swift-users
> On Apr 8, 2017, at 5:22 AM, Hugo Lundin via swift-users > wrote: > > How would I be able to achieve this in Swift? My current idea of this > approach does not seem to work, but also the idea to create specific > subclasses for every type (and then type cast the

Re: [swift-users] Alternative to UnicodeScalar

2017-04-08 Thread Proyb P via swift-users
How do I append character A-Z by integer into CChar and benchmark timing how fast it’s append compare to UInt8? var tmp: [CChar] = [0,0] for var i in 0...256 { tmp[0] = 100 } print(String(cString: )) On Sun, Apr 9, 2017 at 3:17 AM, Proyb P wrote: > Agree, in some case,

[swift-users] Store objects of generic types in a data structure

2017-04-08 Thread Hugo Lundin via swift-users
Dear all, I am currently playing with a concept in Swift to store statistics in apps using generic types. One of the key parts are the ability to register properties (for example booleans, strings and integers - but also more complex data types such as dates): stats.add(description: "iOS

Re: [swift-users] Alternative to UnicodeScalar

2017-04-08 Thread Proyb P via swift-users
I ran with -Ounchecked as most benchmark do, are there more optimization level I'm not aware? On Sun, Apr 9, 2017 at 12:44 AM, Shawn Erickson wrote: > What optimization level did you try this at? You are also including the > print func in your performance test which is a

Re: [swift-users] Swift Concurrency and Actor model

2017-04-08 Thread Proyb P via swift-users
Yeah, I believe Gerard know that, he have been discussed in Vapor slack channel. To add on, Gerard might want to try .Net core and Kotlin. On Sat, Apr 8, 2017 at 4:52 AM, Maxim Veksler via swift-users < swift-users@swift.org> wrote: > Hi Gerald, > > It might be only me I'm not sure what you are

Re: [swift-users] Alternative to UnicodeScalar

2017-04-08 Thread Shawn Erickson via swift-users
What optimization level did you try this at? You are also including the print func in your performance test which is a non-trivial amount of code being executed. Also when in doubt profile the code to see the time spent to better nail down the hotspot locations. If performance issues exist then

[swift-users] Alternative to UnicodeScalar

2017-04-08 Thread Proyb P via swift-users
I have found this took about 0.001s to print 256 characters Compare to Python took 0.16s to print 256 characters, see F8 code and have modify to run only one call instead of 1000 iterations. https://gist.github.com/anonymous/18e372e8d0173e77b5c405920d4d3080 As this is frequently use for