8000 JS: Deprecate type extraction by asgerf · Pull Request #19640 · github/codeql · GitHub
[go: up one dir, main page]

Skip to content

JS: Deprecate type extraction #19640

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

Draft
wants to merge 50 commits into
base: main
Choose a base branch
from
Draft

Conversation

asgerf
Copy link
Contributor
@asgerf asgerf commented Jun 2, 2025

No description provided.

asgerf added 30 commits May 20, 2025 13:19
asgerf added 12 commits May 20, 2025 13:20
Overload resolution has little impact on data flow analysis, because there we care about the concrete implementation of the function, which is the same for all overloads. It can affect the return type, which in turn can affect the call graph we generate, but we'll just have to accept this as overload resolution is too hard without negative recursion.
…nt declarations

This test enforced the opinion that ambient declarations should have no impact on data flow, which is no longer the case. For now I'm just updating the test output.
@github-actions github-actions bot added the JS label Jun 2, 2025
name = spec.getExportedName() and
result = spec.getLocal()
)
or

Check warning

Code scanning / CodeQL

Dead code Warning

This code is never used, and it's not publicly exported.
asgerf added 5 commits June 2, 2025 15:30
This query depended on the cons-hashing performed by type extraction to determine if two types are the same.

This is not trivial to restore, but not important enough to reimplement right now, so for now just simplifying the query's ability to recognise that two types are the same.
name = sig.getName()
)
private class MethodCallSig extends Function {
private MethodSignature signature;

Check notice

Code scanning / CodeQL

Field only used in CharPred Note

Field is only used in CharPred.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0