Nick Lockwood

>What do you think of having a "macro" option for functions and operators Yeah, that's the kind of solution I had in mind. Adding new symbol types would be a...

@wildthink I've written a REPL implementation using a BoxedValue type instead. It works pretty well. I didn't have to reimplement any stdlib operators because I'm just unboxing the values and...

I don't think you can safely use FastCoding with Swift value types that have been bridged to Objective-C.

You can only use Objective-C compatible types with FastCoding. That means classes that inherit from NSObject, where all properties are marked with @objc. It won’t work with structs.

Can anyone confirm if this is still happening in the latest releases? A test case would be extremely helpful.

@fabiankr ah, good point about me not copying the keys. That's a bug on its own regardless of any other side-effects.

I don't understand how this could possibly work. Can you provide a sample project so I can verify before I merge the fix? Thanks.

I checked and it looks like double_t isn't what I thought it was (it's defined as being a minimum of 8 bytes, rather than exactly 8 bytes). I've changed the...

The data shouldn't be misaligned in the first place though: that's the point of the align statement.

I wrote a random map generator in Swift. Maybe I should release that too.