<div dir="ltr">(re-added swift-evolution)<div><br></div><div>I would think so. It's an abbreviation of a given init function, so you would call other self.init() or super.init() functions normally. Saves on complication.<div><br></div><div><br></div><div>Alternatively, perhaps you could do this:</div><div><br></div><div>init(self.foo: String, super.bar: String, super.baz: Int)</div><div><br></div><div>as an abbreviation of</div><div>init(foo: String, bar: String, baz: Int)</div><div>{</div><div> self.foo = foo</div><div> super.init(bar: bar, baz: baz)</div><div>}<br><div><div><br></div><div>I think this would probably require allowing parameters to stay re-orderable, though (in case super's init is "init(baz: Int, bar: String)" ).</div><div><br></div><div><br></div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 14, 2016 at 4:29 PM, Vladimir.S wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">+1. This will make our life easier, it is clear and explicit about the result.<br>
<br>
I assume that there must be a constrain : you can use in init(...) only props introduced in the same class, not in parent class.<div><div><br>
<br>
On 14.04.2016 17:32, Ross O'Brien via swift-evolution wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
init(self.foo: String, self.bar: String, self.baz: Int)<br>
<br>
{<br>
<br>
barCount = bar.characters.count<br>
<br>
}<br>
<br>
}<br>
<br>
<br>
Less boilerplate, more focus on the properties which need to be generated.<br>
<br>
Thoughts?<br>
</blockquote>
</div></div></blockquote></div><br></div></div></div></div></div></div>