You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the feature to automatically add missing direct dependencies does not consider if a discovered dependency is visible to the target under inspection.
Assuming we make no error in matching include statement to target, there are 2 cases we can resolve by implementing this:
If multiple targets in the dependency tree provide a given header we skip this right now with a warning. With visibility we could potentially decide which target to choose.
Even if we find only a single dependency, it might be invalid. If aliases are involved we might add a target which breaks the build, although the added dependency provides the required header.
The text was updated successfully, but these errors were encountered:
Followup to #18
Currently the feature to automatically add missing direct dependencies does not consider if a discovered dependency is visible to the target under inspection.
Assuming we make no error in matching include statement to target, there are 2 cases we can resolve by implementing this:
The text was updated successfully, but these errors were encountered: