-
Notifications
You must be signed in to change notification settings - Fork 121
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
Undriven struct members do not trigger -Wunassigned-variable #829
Comments
Yes, it's intentional. I can add a new warning set for struct members though. |
I'm assuming that a full struct initialization would count as all members having a driver (s = '0). Most code is written this way, it's just the occasional one-off module where the designer uses individual assign statements for each struct member that I've hit a few cases of missed drivers. A new warning here would be great to help push finding the issue to earlier in the process. |
Unsure if this is a bug report or a feature request. The warnings that check for reading unassigned variables has a small gap if that variable is a member of a struct, but this might be intentional.
In the following example, only member 's.a' is driven and 's.b' is undriven.
The text was updated successfully, but these errors were encountered: