From aed4d3898334c265ea76ad260a7573615f87ce38 Mon Sep 17 00:00:00 2001 From: Oliver Schneider Date: Fri, 3 Mar 2017 15:27:33 +0100 Subject: [PATCH] Add decision graph for diagnostics graphviz dot code: ```dot digraph G { A [ label = "Does the message contain\ncode snippets derived\nfrom real code?"] A -> B [ label = "Yes"] A -> C [ label = "No"] B [ label = "Are there multiple\nsnippets that may apply?"] B -> "Guess" [ label = "Yes" ] B -> D [ label = "No" ] D [ label = "Are there situations\nwhere the snippet is plain wrong?"] D -> E [ label = "Yes" ] D -> "Suggestion" [ label = "No" ] E [ label = "Can you detect those\nsituations programmatically?"] E -> G [ label = "Yes" ] E -> "Guess" [ label = "No" ] G [ label = "Suggestion where correct,\nGuess or no code hint otherwise"] C [ label = "Is the message reasonably short?"] C -> "Note" [ label = "Yes" ] C -> "Help" [ label = "No" ] } ``` --- text/0000-guesses.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/text/0000-guesses.md b/text/0000-guesses.md index ca43bf14654..504d16c5bde 100644 --- a/text/0000-guesses.md +++ b/text/0000-guesses.md @@ -201,7 +201,7 @@ This list would get extended by Guesses under the code hint category The complexity is not in the diagnostic levels, but in choosing the correct level for a situation. This is fairly straight-forward for errors vs warnings, but in the sub-diagnostic and code-hint levels, it is less clear. -TODO: add decision graph +![chart](https://cloud.githubusercontent.com/assets/332036/23554529/be228b76-0025-11e7-99e7-627d60f5a328.png) # Drawbacks [drawbacks]: #drawbacks