pghs975uc
/
infer_clone
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a1381565f1'
${ noResults }
infer_clone/infer/tests/codetoanalyze/erlang/topl/issues.exp

8 lines
1007 B
Raw Normal View History Unescape

[erl-frontend] Split generic warning message to specific ones Summary: Previously we just reported NONEXHAUSTIVE_PATTERN_MATCH, which was (1) not correct because not only patterns can cause nonexhaustive behavior, but also guards, and (2) the Erlang runtime reports errors more precisely, indicating whether the nonexhaustive behavior occurs with `if`, `case`, functions or match expressions. Reviewed By: rgrig Differential Revision: D29681637 fbshipit-source-id: 74a25b371
4 years ago
codetoanalyze/erlang/topl/src/topl_taint.erl, fp_test_f_Bad/0, 1, NO_MATCHING_CASE_CLAUSE, no_bucket, ERROR, [no matching case clause here]
codetoanalyze/erlang/topl/src/topl_taint.erl, fp_test_g_Ok/0, 1, NO_MATCHING_CASE_CLAUSE, no_bucket, ERROR, [no matching case clause here]
[topl] Update static matching for Erlang procedures. Summary: Topl matches procedure names against whatever Procname.hashable_name returns. For Java, it returns something like "java.util.ArrayList.add(...)", but for Erlang it used to return something like "add/1": no module and no parenthesis after. Now, Erlang returns "lists:add/1"; that is, it includes module name. Also, Topl doesn't insist anymore on having a paranthesis after the name. Differential Revision: D29520365 fbshipit-source-id: d23be1cc8
4 years ago
codetoanalyze/erlang/topl/src/topl_taint.erl, test_a_Bad/0, 0, TOPL_ERROR, no_bucket, ERROR, [call to source/0,call to sink/1]
[erl-frontend] Translate expression Match Summary: Translates "PATTERN = EXPRESSION". Differential Revision: D29540785 fbshipit-source-id: f17f0938b
4 years ago
codetoanalyze/erlang/topl/src/topl_taint.erl, test_c_Bad/0, 0, TOPL_ERROR, no_bucket, ERROR, [call to source/0,call to sink/1]
[topl] Update static matching for Erlang procedures. Summary: Topl matches procedure names against whatever Procname.hashable_name returns. For Java, it returns something like "java.util.ArrayList.add(...)", but for Erlang it used to return something like "add/1": no module and no parenthesis after. Now, Erlang returns "lists:add/1"; that is, it includes module name. Also, Topl doesn't insist anymore on having a paranthesis after the name. Differential Revision: D29520365 fbshipit-source-id: d23be1cc8
4 years ago
codetoanalyze/erlang/topl/src/topl_taint.erl, test_d_Bad/0, 0, TOPL_ERROR, no_bucket, ERROR, [call to source/0,call to call_sink_indirectly/1,call to call_sink/1,call to sink/1]
codetoanalyze/erlang/topl/src/topl_taint.erl, test_h_Bad/0, 0, TOPL_ERROR, no_bucket, ERROR, [call to dirty_if_argument_nil/1,call to source/0,call to sink/1]
[erl-frontend] Split generic warning message to specific ones Summary: Previously we just reported NONEXHAUSTIVE_PATTERN_MATCH, which was (1) not correct because not only patterns can cause nonexhaustive behavior, but also guards, and (2) the Erlang runtime reports errors more precisely, indicating whether the nonexhaustive behavior occurs with `if`, `case`, functions or match expressions. Reviewed By: rgrig Differential Revision: D29681637 fbshipit-source-id: 74a25b371
4 years ago
codetoanalyze/erlang/topl/src/topl_taint.erl, test_j_Bad/0, 1, NO_MATCHING_CASE_CLAUSE, no_bucket, ERROR, [no matching case clause here]