I'd really love to have `return` in `init`

# language-proposals

[elect]

I'd really love to have return in init

[louiscad]

Use case?

[elect]

relative big init for an helloOpenVR app

[louiscad]

Also, what about properties declared below, and other init blocks? Better do an if

[louiscad]

Or call methods from your init block

[elect]

uhm, yeah, also

[elect]

the calls from the block doesnt play nice with `val`s expecting to be set

[louiscad]

Organizing your code is important.

[louiscad]

You can assign `val`s from something computed in a method

[louiscad]

even in init block as long as you don't call something initialized after it's supposed to run

[elect]

last time I checked, I couldnt

[elect]

I'll check again, thanks

[benleggiero]

return null would be nice for failable convenience initializers

[Andreas Sinz]

if you are doing alot of initializiation inside init, you should think about putting this code into a factory method

[benleggiero]

@Andreas Sinz I don't see why. To me, the syntax is less clear; not all initializers are called the same way and the caller isn't guaranteed a clear reason why.

If a future version of the library is updated such that the factory method doesn't do "a lot of initialization", should it be removed in favor of a common constructor? When is the amount is initialization "a lot", causing it to be moved to a factory method? Etc

[elect]

@Andreas Sinz the nice thing about init is val values

[Andreas Sinz]

@elect can you give me an example where you have to use a var because you are using a factory method?

[elect]

uhm, I'd need to think about

[elect]

maybe you are right

[Andreas Sinz]

i'm just genuinely asking, I've never come across an instance where a factory method forced me to have a var instead of a val

[elect]

I'll keep it in mind if I will ever cross it

[elect]

because at the moment I cant afford to dedicate time to that

[Andreas Sinz]

@benleggiero if you do the initialization of properties inside the class you are violating the Single Responsibility Principle. I usually don't use init { } at all, only when its necessary because of some library/framework I'm using

[benleggiero]

@Andreas Sinz same here. I just don't want to compromise my API because the library I'm using has, for instance, a constructor that throws an exception like URL