Re: [swift-users] Coding style for internal/private variables

A little bit off-topic: Is there any way to create autocompletion shortcuts in Xcode that will show only private, internal or both values of an instance? class Foo { private var integer: Int = 0 internal var string: String = "foo" internal func boo() {} } let instance = Foo()

Re: [swift-users] UnsafeMutablePointer vs. UnsafeMutablePointer

This shouldn't be something you need to worry about. The mechanism the OS uses to handle memory per process is different from the mechanism your process uses to allocate memory, and the OS should reclaim all the memory that your app used (whether it was 'leaked' or not). More info:

Re: [swift-users] Coding style for internal/private variables

I never liked the underscores (so for me, they have been the best choice to mark stuff I should not know of in Cocoa ;-). For several years, I prefixed instance variables with "m", but stopped doing so after a talk about bad habits in writing Java code: It is like Hungarian notation, which also

Re: [swift-users] UnsafeMutablePointer vs. UnsafeMutablePointer

I’ve got one more question that bothers me. Lets say I’ve got a class that might look something like this: class Reference { var pointer: UnsafeMutablePointer init(integer: Int) { self.pointer = UnsafeMutablePointer.alloc(1) self.pointer.initialize(integer)

[swift-users] Coding style for internal/private variables

I’d like to talk about your personal coding styles in swift for its access control. Remember these variable names like __magic or _spell or even garbage_? Sure swift solves the synthesize problem but there might be old habits that let us write such code. Here are some examples: internal

Re: [swift-users] Can't get Error pattern matching to work cross framework and command line tool

Thank you! -Joe > On May 31, 2016, at 9:49 PM, Joakim Hassila wrote: > > Hi Joe, > > Absolutely, I just filed rdar://26569913 (used Radar according to community > guidelines of putting projects requiring Xcode to reproduce there). > > I hope I captured the dependencies /