<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Since we know the types of the properties, how about we replace the type in the signature with either an indication that the property should be automatically set, or better yet, the property which should be set:</div><div class=""><br class=""></div><div class="">class Foo</div><div class="">{</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>let foo : String</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>let bar : String</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>let barCount : Int</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>let baz : Int</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>init(foo: self.foo, bar: self.bar, baz: self.baz)</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>{</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>self.barCount = bar.characters.count</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>} </div><div class="">}</div><div class=""><br class=""></div><div class="">That way you don’t always have to have the init’s parameter names match the names of the properties they set (even though they often would). We could also allow a leading dot as a shorthand for ‘self.’</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>init(foo: .foo, bar: .bar, baz: .baz)</div><div class=""> </div><div class="">I think I like explicit ‘self.’ better, but that may just be my preference. In either case, the generated interface would show the actual type.</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>// init(foo: String, bar: String, baz: Int)</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Jon</div><div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">This is a common pattern for initialisers at the moment:
class Foo
{
let foo : String
let bar : String
let barCount : Int
let baz : Int
init(foo: String, bar: String, baz: Int)
{
self.foo = foo
self.bar = bar
self.baz = baz
barCount = bar.characters.count
}
}
This involves a lot of using 'self.'. For those who prefer not to use
'self.' explicitly everywhere, this is probably the main place it gets
used. It's a lot of boilerplate code.
How would it be if, like default variables, we could pack some of that
information into the argument tuple, and unify parameters with properties
immediately?
class Foo
{
let foo : String
let bar : String
let barCount : Int
let baz : Int
init(self.foo: String, self.bar: String, self.baz: Int)
{
barCount = bar.characters.count
}
}
Less boilerplate, more focus on the properties which need to be generated.
Thoughts?</pre></blockquote><div class=""><br class=""></div></div></body></html>