New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SR-8354] Runtime warning on failure to demangle type #50882
Comments
@jckarter, does this look familiar? |
Haven't seen this one, looks like the runtime demangler is missing a case. |
@swift-ci create |
This is fixed on master at 191db1e. Not sure if it was part of my recent refactoring. |
Comment by David Kopec (JIRA) Did this fix make it into the final version of Swift 4.2 that ships with Xcode 10? I am still seeing it in a Playground when the page "Chapter 3" of the Playground in this repository runs under the Mac App Store version of Xcode 10/Swift 4.2: https://github.com/davecom/ClassicComputerScienceProblemsInSwift This did not exist in Xcode 9/Swift 4.1.2. Thanks. |
It is not fixed in Swift 4.2, unfortunately, but the warning is harmless in most cases and can be ignored. |
Comment by Ray Fix (JIRA) I am glad it appears that a big refactoring appears to have solved it. If it is harmless and ignorable, could it be commented out on 4.2 so the message is not emitted? This would help improve playgrounds as a learning platform. |
Comment by David Kopec (JIRA) I have to agree with this. To a new user experiencing a Playground, this appears to be a serious error, when really it is harmless. It would be optimal to get a fix sooner rather than later. Thanks. |
Yes, I disabled the message in playgrounds (and made the warnings more descriptive) in this PR: #19416 |
Environment
Swift 4.2 (Xcode 10 beta 4)
Swift 4.2-dev master branch (c2452cf)
Additional Detail from JIRA
md5: 95c81544b19c358f5ecb8e2fcc8f5d4f
is duplicated by:
Issue Description:
Running the following code will result in the output below.
This doesn't occur in Swift 4.1.2. The output there is:
The text was updated successfully, but these errors were encountered: