-
Notifications
You must be signed in to change notification settings - Fork 1.9k
internal: add failing incremental test #8721
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
Conversation
| assert_eq!(module_data.scope.resolutions().count(), 4); | ||
| }); | ||
| let n_recalculated_item_trees = events.iter().filter(|it| it.contains("item_tree")).count(); | ||
| assert_eq!(n_recalculated_item_trees, 1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jonas-schievink currently this returns 4 rather than 1. That is, we recalculate item_tree for file itself, as well as for each of the macro calls. Am I correct that we don't expect this happening?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah that shouldn't happen
Co-authored-by: Jonas Schievink <jonasschievink@gmail.com>
|
Current guess: it's to_fragment_kind |
|
ItemTrees for macro files seem to have a lot of unexpected query dependencies: I would expect just 2: |
|
Seems like these are all from |
|
Making |
|
Ah, that's probably just because |
In theory yes, but |
No description provided.