I really need to do a regular open source clinic post: send in up to 30 or 40
standalone lines that compile under 2.2 and won't under 3, with a description
of expected behavior and test cases.
You can reach out for help on irc.freenode.net in #swift-lang, there are
several peer-support slack ch
The Swift migrator as used in Xcode 7.3 is not open-source, so it’s not
included in the downloadable toolchains. I’m afraid you’ll have to migrate your
project by hand at this point. The compiler should give you some help in its
diagnostics, at least.
Apologies,
Jordan
> On Jun 1, 2016, at 10:
Hi Charles,
Trunk Development toolchain was created from master branch, and Swift 3.0
Preview 1 toolchain was created from swift-3.0-preview-1-branch.
Difference between master and swift-3.0-preview-1-branch:
https://github.com/apple/swift/compare/swift-3.0-preview-1-branch
Master branch: ht
I see that there is a ‘Trunk Development(master)’ and the 'Swift 3.0 Preview 1
Release Branch’ both from May 31, 2016.
Is there any difference in these two releases?
Thanks,
Chuck Lane
___
swift-users mailing list
swift-users@swift.org
https://lists.sw
How's the workload nowadays? You were pretty stressed last i checked.
On Monday 30 May 2016, wrote:
> Send swift-users mailing list submissions to
> swift-users@swift.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.swift.org/mailman/listinfo/swi
Hi all,
I want to start testing Swift 3.0 in one of my projects. However code
conversion seems not to be supported "The active toolchain, “Swift 3.0
Preview 1 Snapshot 2016-05-31 (a)”, does not have a Swift converter.".
is it planned to have it included soon? any workarounds to have automatic
con
I think the IDE should colorize differently these variable names.
> On 01 Jun 2016, at 18:02, Adrian Zubarev via swift-users
> wrote:
>
> 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 garb
@Austin: do you use self._name or just _name in your code?
I’ve seen self._name usage in swifts standard libraries and didn’t liked it at
first glance, but it feels alright now.
My personal habit is to write self. everywhere it’s possible, because as soon
as some private variable is nested insi
>From what I've observed, preceding (rather than trailing) single underscores
>indicate private use. The standard library includes a fair number of "Apple
>Internal" (I guess now "Swift Team Internal") variables, methods, functions,
>etc that follow this practice. This practice is, as far as I c
I've actually used the _underscore convention in Swift to denote "private"
members that nobody outside the type should touch, but that I want to expose to
an extension on that type defined in a different file. It's a convention that
works decently well with a little discipline.
Some time back,
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()
instan
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:
http://stac
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 p
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)
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 _name
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 / reproduction steps p
16 matches
Mail list logo
