Xcode-beta (15.0) C++ interop option generates erroneous 'let' property initialization code

[ByunghoonKim]

Description

Steps to reproduce

1. Install Xcode 15.0 beta (15A5160n). Create a new macOS app project. Placeholder code compiles well.
2. set Xcode > Settings > Command Line Tools: Xcode-beta 15.0 (15A5160n)
3. choose Project > Build Settings > Swift Compiler - Language > C++/Objective-C++, and build
4. Build fails

Expected behavior
Compile & Run

Environment

• Swift compiler version info

swift-driver version: 1.82.2 Apple Swift version 5.9 (swiftlang-5.9.0.114.6 clang-1500.0.27.1)
Target: arm64-apple-macosx13.0

• Xcode version info

Xcode 15.0
Build version 15A5160n

• Deployment target:

macOS 13.4

[hyp]

@egorzhdan are you looking into this one?

[egorzhdan]

I cannot reproduce this with a newly created macOS App project.
@ByunghoonKim could you please elaborate on how you are creating the project in Xcode?

[ByunghoonKim]

I have done nothing special other than what I described in the original post.

I am working on a 2021 MacBook Pro (M1 Pro) with Ventura 13.4. To be sure, I have deleted both Xcode 14 and Xcode 15 beta, re-installed Xcode 15 beta, and rebooted my laptop twice just now.
This is what happens. (sorry for the movie quality. had to make it under 10MB)

Screen.Recording.2023-06-21.at.10.49.30_540p.mp4

[ByunghoonKim]

Hi,
I am here to report that the issue I described above has disappeared with Xcode 15 beta 3. The erroneous code generation has, however, continued to be problematic with beta 2.

Because I see no pull request regarding this issue, I do not know if the underlying problem, if any, is actively resolved, or it was mere a symptom of something else that has been patched with beta 3. In any case, since my problem is gone, I'd like to ask if it would be helpful for your workflow if I closed this issue.

Thank you for the update, anyway. :)

[egorzhdan]

Thanks @ByunghoonKim for the update! Glad to know this is no longer an issue for you.

Unfortunately the underlying issue is not yet fixed, we're tracking it as rdar://110431818 internally.

[ByunghoonKim]

If that is the case, I will leave it open for now. Thanks again for the effort, @egorzhdan.

[hyp]

I will close this issue since it does not reproduce with Beta 3 anymore. If this reoccurs we can reopen it.