aboutsummaryrefslogtreecommitdiffstats
path: root/lib/dialyzer/test/map_SUITE_data
diff options
context:
space:
mode:
authorMagnus Lång <[email protected]>2016-02-28 00:25:32 +0100
committerHans Bolinder <[email protected]>2016-04-28 16:16:09 +0200
commite16ff38bd1f235eefa0fbee87e9ee6dd0fc94e2a (patch)
treebc0c8cd399c0f8e070427eee80b4dff3b140148d /lib/dialyzer/test/map_SUITE_data
parentebd967522612333e52a884181e6132b1ba7e5239 (diff)
downloadotp-e16ff38bd1f235eefa0fbee87e9ee6dd0fc94e2a.tar.gz
otp-e16ff38bd1f235eefa0fbee87e9ee6dd0fc94e2a.tar.bz2
otp-e16ff38bd1f235eefa0fbee87e9ee6dd0fc94e2a.zip
dialyzer_dataflow: Fix try in guards
The assumption that 'try' nodes were only used to wrap entire guards is no longer true. We're still swallowing warnings when the handler returns successfully. Unfortunately, bind_guard/5 would need to be refactored to return a new state in order to generate those warnings.
Diffstat (limited to 'lib/dialyzer/test/map_SUITE_data')
-rw-r--r--lib/dialyzer/test/map_SUITE_data/results/guard_update3
1 files changed, 0 insertions, 3 deletions
diff --git a/lib/dialyzer/test/map_SUITE_data/results/guard_update b/lib/dialyzer/test/map_SUITE_data/results/guard_update
index f6200ae2af..e4bc892195 100644
--- a/lib/dialyzer/test/map_SUITE_data/results/guard_update
+++ b/lib/dialyzer/test/map_SUITE_data/results/guard_update
@@ -1,7 +1,4 @@
-guard_update.erl:12: Function t2/0 has no local return
-guard_update.erl:15: Clause guard cannot succeed. The variable M was matched against the type #{'a':=2}
-guard_update.erl:15: Function f2/1 has no local return
guard_update.erl:5: Function t/0 has no local return
guard_update.erl:6: The call guard_update:f(#{'a':=2}) will never return since it differs in the 1st argument from the success typing arguments: (#{'b':=_, ...})
guard_update.erl:8: Clause guard cannot succeed. The variable M was matched against the type #{'a':=2}