Skip to content
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

Ruby: Include more (hash) splat flow in type tracking #13997

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

hvitved
Copy link
Contributor

@hvitved hvitved commented Aug 18, 2023

Whilst reviewing #13938, it occurred to me that we don't include the read/store steps used to model flow into (hash) splat parameters in type tracking. This PR does that, but a bit differently, as we use type tracking's ability to define read-store steps, to avoid having SynthSplatParameterElementNodes be LocalSourceNodes.

@github-actions github-actions bot added the Ruby label Aug 18, 2023
@hvitved hvitved added the no-change-note-required This PR does not need a change note label Aug 21, 2023
@hvitved hvitved marked this pull request as ready for review August 21, 2023 11:06
@hvitved hvitved requested a review from a team as a code owner August 21, 2023 11:06
@calumgrant calumgrant requested a review from hmac August 21, 2023 13:27
@hmac
Copy link
Contributor

hmac commented Aug 21, 2023

It looks like the DCA run failed - it would be good to see a passing run for this change. I'd also be interested to know: do we expect this to result in any change in analysis results? Presumably only for queries which rely on type tracking rather than full data flow?

@hvitved
Copy link
Contributor Author

hvitved commented Aug 21, 2023

It looks like the DCA run failed - it would be good to see a passing run for this change. I'd also be interested to know: do we expect this to result in any change in analysis results? Presumably only for queries which rely on type tracking rather than full data flow?

The first DCA run is successful; the second fails with Cannot create a string longer than 0x1fffffe8 characters because meta queries are enabled (I believe @esbena is already aware of this). Regarding analysis results: Yes, we can expect different analysis results, because type tracking is used to construct the call graph.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-change-note-required This PR does not need a change note Ruby
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants