ksm / swiftinflux Goto Github PK

Beta 3 change + Chris Lattner's response: https://devforums.apple.com/message/1112830#1112830

I think we shouldn't list Swift bugs on SwiftInFlux at all. Here's why:

1. There's a ton of bugs in Swift — most of which are obvious to be bugs once you encounter them
2. … yet we list only three of them: https://github.com/ksm/SwiftInFlux#enums-nested-in-generic-classes-broken https://github.com/ksm/SwiftInFlux#unowned-references-breaking-in-beta-2-and-3 https://github.com/ksm/SwiftInFlux#recursive-nested-functions
3. The bugs we list are quite random (there are some more obvious/more important ones)
4. … and I don't think anyone checked recently if they are still present in Beta 5
5. There's a lot of stargazers to SwiftInFlux, but not too many contributors — no one is adding new bugs to the list
6. You can almost certainly expect that bugs will be fixed. It's the new features and semantic changes that are most interesting tidbits to be found, collected and listed.

Thoughts?

I'm on my phone right now and I just got this answer so I'd like to leave this here before I forget:
https://devforums.apple.com/message/1100335

Xcode error messages + https://devforums.apple.com/message/1022374#1022374. Also the fact that "The feature set for 1.0 is nearly final" would be worth noting somewhere.

Anyone?

Found via http://stackoverflow.com/a/27109202/195691, adding @objc to extension properties and methods allows them to be overridden:

import Foundation
class Base { }

extension Base {
    @objc var foo: String { return "foo" }
}

class Sub: Base {
    override var foo: String { return "FOO" } // This no longer errors
}

This may be a bug in the @objc implementation, however, as when I try this in an iOS Playground I get a runtime error when instantiating Sub(), but it works in an OS X playground and in the command line swift REPL.

https://twitter.com/jckarter/status/613423812332294144

The next line is not working in beta 6.3 XCode.

let error: NSError var newUserInfo = error.userInfo as? [NSObject: NSObject] ?? [:]

https://devforums.apple.com/message/1031354#1031354

https://mobile.twitter.com/jl_hfl/status/609668243146559488

In beta 5 optional value types are now mutable. You should update this under changed in beta 5.

someValueArray?.removeAtIndex(0) for example, is now valid.

Also assignment in possible through ?

E.g. someObject?.stringVar = "some string" before beta 5 this had to be done with !

https://twitter.com/gparker/status/611990857034563584

This code:

enum SomeEnum {
  case SomeCase(label: SomeValue)
}

Works again. I tested it on 6.1.1 and 6.1 and it works on both, but I don't know if it wasn't actually fixed before that. Does anyone have 6.0.1 to verify?

To write up: https://devforums.apple.com/message/1129274#1129274

please do contribute.

https://mobile.twitter.com/radexp/status/583257913508126720 + Joe's answer

Many changes, like error handling and protocol extensions. :)

The relevant sections of the document need updating.

I just installed Xcode 6 beta 4 and my convenience inits don't work anymore.

It says Could not find an overload for init that accepts the supplied arguments

`class MyController: UIViewController{

convenience init() {
    self.init(nibName: "CreditOptionsView", bundle: nil)
}

}`

It happened too with a convenience initialiser for UIViewController self.init(rootViewController: viewController)

Why?
It was working in the Xcode 3 beta 2

I wonder if we should delete this: https://github.com/ksm/SwiftInFlux#set-of-legal-operator-characters

With Beta 4, the official Swift book acknowledges that you can use certain Unicode characters in operator names: https://developer.apple.com/library/prerelease/mac/documentation/Swift/Conceptual/Swift_Programming_Language/AdvancedOperators.html#//apple_ref/doc/uid/TP40014097-CH27-XID_85

It doesn't actually change anything, so it doesn't make sense to move it to "Changed", so perhaps we should just delete it?

This: https://devforums.apple.com/message/1101833#1101833

• describe the Box workaround and why it's needed

Anyone wants to write up?

good resource, as always: http://airspeedvelocity.net/2014/09/10/changes-to-the-swift-standard-library-in-xcode-6-1/

https://mobile.twitter.com/getaaron/status/611655848537026560

Hi, between 6.1 und 6.2 there was a 6.1.1 release with some changes / bug fixes to swift.

https://mobile.twitter.com/jckarter/status/609776558153187328

https://devforums.apple.com/message/1028133#1028133

anyone wants to write up? ;)

Mirror was added to the Swift Standard Library Reference on 7/21/2015. The article Simple Reflection in Swift is from 2014. I'm just learning about these these concepts in Swift but happy to make a PR once I have a better idea of how I would change the Reflection section.

Sorry for the poor wording. Just writing in to note something that had previously worked in XCode 6.0 and fails to work on XCode 6.1.

Example of offending code:

class GameScene: SKScene, UIGestureRecognizerDelegate {
    var scoreLabel = SKLabelNode(fontNamed: "American Typewriter")
    ...

Further discussion

https://stackoverflow.com/questions/26836102/crash-on-instantiating-sklabelnode-swift-ios-8-1?noredirect=1#comment42243455_26836102