Private init unexpectedly calls ExpressibleByIntergerLiteral init

[laclouis5 (Lac Louis)]

Again, I perfectly understand and support the rationale of the proposal but I'm still not convinced that "changing the language to mach [their] expectation" did solve this issue. We now have a magic behavior that is really difficult to discover. I'm not even sure that this is stated somewhere in the documentation or in the Swift Programming Language book.

This is unfortunate since good alternatives were proposed in the proposal's discussion thread:

@Brent_Royal-Gordon

However, it's not difficult to teach developers to use as. Usually what's happening is that their mental model of the language is wrong: they think of UInt16(foo) as a cast to a primitive type, and are surprised to learn that it's actually an initializer on a struct and they're initializing an instance. Learning this helps them understand how the language works, what the difference is between initializers and as, and how they can write the same things they see in the standard library types.

I think actually turning this into magic would be counterproductive. The better solution is to make the compiler replace me in that story, by having it emit a warning with a fix-it. It keeps initializer calls meaning exactly what they say. (And it doesn't require an evolution proposal to do, since you can add a warning with a mere bug.)

Wouldn't this solution have both solved the issue and helped educate users while still keeping the language semantic consistent?

Anyway, I don't want to highjack this post to discuss a past decision as my issue is now solved, thanks again!