Way too meta
What about Swift? If you've looked closely at the Swift Language Reference you'll see two short paragraphs describing
SomeClass.Type, a short example (that doesn't address
Type at all), and that's it.
In Swift, all types have metatypes, not . . .
Here is a quick rundown of some of the changes in Beta 5 posted today. For the full details as always check out the release notes
- Structs and classes can conform to
- Non-failable initializers can now chain to failable initializers by using
- Debug builds should have better performance due to using pre-specialized generics in the . . .
Mirror struct now has a
children property that you can indeed iterate over so this isn't really applicable anymore but the sequence stuff is still relevant. You can check out Rob Napier's post about AnySequence for more info.
I've been playing with the new reflection API in Swift 2 and found one constant annoyance:
. . .
Single Instruction, Multiple Awesome
Swift 2 brings updated support for SIMD (Single Instruction Multiple Data). What exactly does that mean?
Each CPU vendor has their own unique snowflake versionº but the premise is the same: process data in parallel chunks. Each SIMD instruction operates on a group of values organized into what are called "lanes". . . .
A quick recap for those who haven't parsed the release notes yet:
- Enum cases with values can be used as a function; basically the compiler automatically creates a function that accepts parameters matching the case's values and returns that enum case with the values filled in.
- Non-mutating methods of structs, enums, and . . .
As everyone is no doubt aware Swift 2 was announced at WWDC. I'm going to do a series of posts on the changes but for now let's just cover the major points:
- Global and free-standing functions now follow the same parameter label rules as methods. The
#external name syntax is gone.
- Multi-payload enums basically allow . . .
Reabstraction eats the world
This is an update on a previous post.
First, @jckarter pointed out that
swift_func_object is an artifact of the implementation. Swift is reabstracting the function to promote it to the most generic form (it's how a
()->Int can be passed to something expecting
()->Void). It turns out that Swift lifts functions to the maximally . . .