Skip to content

Conversation

jbj
Copy link
Contributor

@jbj jbj commented Oct 10, 2018

This is the same change as in #276, just for a similar query. Requested in https://discuss.lgtm.com/t/false-alarm-for-unreachable-unsigned-comparison-to-zero/1392.

jbj added 2 commits October 10, 2018 17:04
It still runs on uninstantiated templates because its underlying
libraries do. It's not clear whether that leads to other false
positives, but that's independent of the change I'm making here.
@jbj jbj added the C++ label Oct 10, 2018
Copy link
Contributor

@geoffw0 geoffw0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

I think analysing the templates themselves (we sometimes call these 'uninstantiated templates', but I'm not fond of the term) should be OK, as any comparison involving a template parameter would either not be populated at all or not have a type this query understands.

@geoffw0 geoffw0 merged commit 3b8c72b into github:master Oct 12, 2018
@geoffw0 geoffw0 mentioned this pull request Nov 20, 2018
aibaars pushed a commit that referenced this pull request Oct 14, 2021
Use integer comparisons instead of strings when scanning ERB files
smowton pushed a commit to smowton/codeql that referenced this pull request Apr 16, 2022
Add delegated property tests and adjust extraction
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.

2 participants