51369b610e
When an include is not surrounded by empty lines, its content is inlined on the same line as the adjacent content. That can lead to broken tags and other display issues. This PR fixes all such includes and introduces a validation step that forbids introducing the same problem again.
61 lines
1011 B
Plaintext
61 lines
1011 B
Plaintext
== Why is this an issue?
|
|
|
|
Jump statements, such as ``++return++``, ``++yield break++``, ``++goto++``, and ``++continue++`` let you change the default flow of program execution, but jump statements that direct the control flow to the original direction are just a waste of keystrokes.
|
|
|
|
=== Noncompliant code example
|
|
|
|
[source,csharp]
|
|
----
|
|
void Foo()
|
|
{
|
|
goto A; // Noncompliant
|
|
A:
|
|
while (condition1)
|
|
{
|
|
if (condition2)
|
|
{
|
|
continue; // Noncompliant
|
|
}
|
|
else
|
|
{
|
|
DoTheThing();
|
|
}
|
|
}
|
|
return; // Noncompliant; this is a void method
|
|
}
|
|
----
|
|
|
|
=== Compliant solution
|
|
|
|
[source,csharp]
|
|
----
|
|
void Foo()
|
|
{
|
|
while (condition1)
|
|
{
|
|
if (!condition2)
|
|
{
|
|
DoTheThing();
|
|
}
|
|
}
|
|
}
|
|
----
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
include::../message.adoc[]
|
|
|
|
include::../highlighting.adoc[]
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
include::../comments-and-links.adoc[]
|
|
|
|
endif::env-github,rspecator-view[]
|