From e16ff38bd1f235eefa0fbee87e9ee6dd0fc94e2a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Magnus=20L=C3=A5ng?= Date: Sun, 28 Feb 2016 00:25:32 +0100 Subject: 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. --- lib/dialyzer/test/map_SUITE_data/results/guard_update | 3 --- 1 file changed, 3 deletions(-) (limited to 'lib/dialyzer/test/map_SUITE_data/results/guard_update') 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} -- cgit v1.2.3