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-15163] Failed to produce diagnostic for expression #395
Comments
cc @xedin |
Comment by Marcus Neal (JIRA) if the Json file is needed to understand the structure of the model, I can provide a copy. thanks theindigamer (JIRA User) |
Comment by Marcus Neal (JIRA) Good afternoon. Want to get an update on this bugs. Thanks |
@swift-ci create |
For diagnostic bugs, I would recommend trying to comment out lines until you can get a better diagnostic and slowly add things back while things type-check. You can also try breaking up things into smaller functions and properties. |
Comment by Marcus Neal (JIRA) thanks theindigamer (JIRA User) the below code is what is causing the diagnostic error, but still unable to know the root cause /* if let characters = homeData.fetchedPorn{
|
I have reduced attached code down to:
With main branch that would produce multiple diagnostics - a couple related to `autocapitalization` because it doesn't exit on `TextField` and another for `ForEach(characters) {data}` -> `referencing initializer 'init(_: content🙂' on 'ForEach' requires that 'VideoVideo' conform to 'Identifiable'` - which is I guess the primary issue because `VideoVideo` indeed doesn't conform to `Identifiable` protocol. |
Knowledgeink (JIRA User) Could you please verify that the issue has been resolved in main branch and/or Xcode 13? |
Adopt the Swift Parser
Attachment: Download
Additional Detail from JIRA
md5: 4c7cb6fb60d466ffc893961c48019150
Issue Description:
Attempting to make an api call, unable to identify why I am getting the below message.
Failed to produce diagnostic for expression; please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the project
The text was updated successfully, but these errors were encountered: