-
Notifications
You must be signed in to change notification settings - Fork 226
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
Add support for TupleExpressions in CSharpExplodedGraph #2933
Labels
Area: CFG/SE
CFG and SE related issues.
Comments
pavel-mikula-sonarsource
added
Area: CFG/SE
CFG and SE related issues.
Type: Improvement
labels
Jan 2, 2020
costin-zaharia-sonarsource
added a commit
that referenced
this issue
Feb 12, 2020
Since the tuples are not yet fully supported by both CFG and symbolic execution (#2933) we will ignore the methods which are containing them.
costin-zaharia-sonarsource
added a commit
that referenced
this issue
Feb 12, 2020
Since the tuples are not yet fully supported by both CFG and symbolic execution (#2933) we will ignore the methods which are containing them.
costin-zaharia-sonarsource
added a commit
that referenced
this issue
Feb 12, 2020
Since the tuples are not yet fully supported by both CFG and symbolic execution (#2933) we will ignore the methods which are containing them.
closing as this will be fixed with the new Roslyn CFG |
@andrei-epure-sonarsource I'd prefer to keep this documented as opened issue until we support it. |
@pavel-mikula-sonarsource can we close this now? |
pavel-mikula-sonarsource
closed this as not planned
Won't fix, can't repro, duplicate, stale
Jan 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We need to add support for handling TupleExpressions in CSharpExplodedGraph.
Repro steps
Currently the TupleExpressions are just ignored when processing code like:
Additional notes
Once the tuples are supported by CFG and semantic execution we need to update the DeadStores rule (S1854) and remove the check added by #3113.
The text was updated successfully, but these errors were encountered: