First and foremost, I want to clarify that I am mostly interested in how to ask this question, so that I get the kind of answer I want. I have the feeling the compiler warning the question was about is not as innocent as a simple style preference. So I want to know how the original question was unclear, and how any of my edits could be perceived as changing the question.

I asked a question on the main site, and in every version of the question, the main question boiled down to 

> 
> What does "The corresponding then clause does not complete normally"
>  mean?
> 
> 
> 

That wording is in every version of the question, is referencing an explicit compiler warning, and (I thought) is obviously a technical question. The question explicitly states this was a compiler warning output. A good answer, therefor, should have references to either documentation, or examples as to why this compiler warning exists.

I asked a couple more questions with the intent to reinforce the fact that I want a technical answer. Here is the full question statement...

> 
> So in all, What does "The corresponding then clause does not complete
>  normally" mean? Does this affect code execution, or is it simply a
>  formatting preference? If this isn't just a cosmetic issue, then what
>  are the risk/side effects?
> 
> 
> 

Apparently, there was ambiguity, and I got this [answer](https://stackoverflow.com/posts/49945189/timeline), which started a small edit war as I tried to make the question more clear. Since that answer gave no support for it's 1 line technical argument, and then went on to talking about style, I feel it never really answered the question for any version of it (but was still related enough to qualify as an answer). The very last question, asking for possible non-style problems with this warning, very explicitly makes style arguments not an answer (I thought).

Here is the [question](https://stackoverflow.com/q/49944900/6893866), and its [timeline](https://stackoverflow.com/posts/49944900/timeline).

So, what part of this question made it sound like anything other than a purely technical issue?