@bavarious is blocked

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @bavarious.

  1. And I’m not surprised, App Store.app.

  2. The Last Line Effect: The probability of a making a mistake in the last pasted block of code is 4 times higher:

  3. I appreciate ’s 5.1.3 release notes detailing the lost no-OTR /query messages bug:

  4. could not build Objective-C module / A fatal parse error has occurred. LLDB may become unstable; please restart your debug session ASAP. 😒

  5. 10.10.3’s kernel log messages look… beheaded. 🂽

  6. $ find /Applications -name libswiftCore.dylib …BAVClock.app… …GitHub.app… …Leaf.app… …Xcode.app…

  7. And no completion love for instance methods.

  8. Xcode 6.2 & Objective-C + Swift oddities.

  9. Today I used ; to end a statement in Swift.

  10. Swift feature or bug? /cc

  11. Apparently Swift doesn’t like properties standing alone.

  12. Swift TIL: given a Comparable type T, Optional<T> is also a strict total order with nil being the least element.

  13. Needed to specify a (Swift 1.1) branch for a transitive dependency in Carthage. Doing that in the main Cartfile worked; unsure if it should.

  14. In reply to

    . What if it’s a user-defined type? Do I need to know the module name (think playgrounds) in advance?

  15. Hrm. enum E { case String(String) } Use of undeclared type ‘String’.

  16. Bavarious followed , , and 4 others
    • @NoorDotKhan

      League of Legends Enthusiast & Software Developer

  17. ‘Xcode 6.1b3 is definitely not the final build of Xcode 6.1.’

  18. Interestingly enough, the problem only manifested itself when a window presented a sheet after the faulty code.

  19. Spent a couple of hours debugging third party code until realising it was mismatched -save/restoreGraphicsState in a bunch of nested cases 😤

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·