From 39631054c58df5841ea268b7002b820ec55f6e0a Mon Sep 17 00:00:00 2001 From: Dmitry Jemerov Date: Thu, 3 Dec 2015 16:22:11 +0100 Subject: restructure Dokka build to use Gradle for everything except for the Maven plugin --- test/data/classes/annotatedClass.kt | 1 - .../annotatedClassWithAnnotationParameters.kt | 1 - test/data/classes/classWithCompanionObject.kt | 7 - test/data/classes/classWithConstructor.kt | 1 - test/data/classes/classWithFunction.kt | 4 - test/data/classes/classWithProperty.kt | 3 - test/data/classes/companionObjectExtension.kt | 10 - test/data/classes/dataClass.kt | 1 - test/data/classes/emptyClass.kt | 3 - test/data/classes/emptyObject.kt | 3 - test/data/classes/genericClass.kt | 3 - test/data/classes/indirectOverride.kt | 9 - test/data/classes/innerClass.kt | 5 - test/data/classes/javaAnnotationClass.kt | 5 - test/data/classes/notOpenClass.kt | 7 - test/data/classes/sealedClass.kt | 1 - test/data/classes/secondaryConstructor.kt | 5 - test/data/comments/directive.kt | 35 - test/data/comments/emptyDoc.kt | 1 - test/data/comments/emptyDocButComment.kt | 2 - test/data/comments/emptySection.kt | 6 - test/data/comments/multilineDoc.kt | 7 - test/data/comments/multilineDocWithComment.kt | 8 - test/data/comments/multilineSection.kt | 7 - test/data/comments/oneLineDoc.kt | 2 - test/data/comments/oneLineDocWithComment.kt | 3 - test/data/comments/oneLineDocWithEmptyLine.kt | 3 - test/data/comments/section1.kt | 5 - test/data/comments/section2.kt | 6 - test/data/format/accessor.kt | 5 - test/data/format/accessor.md | 18 - test/data/format/annotatedTypeParameter.kt | 2 - test/data/format/annotatedTypeParameter.md | 8 - test/data/format/annotationClass.kt | 1 - test/data/format/annotationClass.md | 14 - test/data/format/annotationParams.kt | 1 - test/data/format/annotationParams.md | 8 - test/data/format/annotations.kt | 6 - test/data/format/annotations.md | 26 - test/data/format/bracket.html | 14 - test/data/format/bracket.kt | 4 - test/data/format/brokenLink.html | 14 - test/data/format/brokenLink.kt | 4 - test/data/format/classWithCompanionObject.html | 46 - test/data/format/classWithCompanionObject.kt | 7 - test/data/format/classWithCompanionObject.md | 26 - test/data/format/codeSpan.html | 14 - test/data/format/codeSpan.kt | 4 - test/data/format/companionObjectExtension.kt | 10 - test/data/format/companionObjectExtension.md | 23 - .../crossLanguage/kotlinExtendsJava/Bar.html | 37 - .../format/crossLanguage/kotlinExtendsJava/Bar.kt | 6 - .../crossLanguage/kotlinExtendsJava/test/Foo.java | 6 - test/data/format/deprecated.class.html | 41 - test/data/format/deprecated.kt | 5 - test/data/format/deprecated.package.html | 43 - test/data/format/emptyDescription.kt | 5 - test/data/format/emptyDescription.md | 11 - test/data/format/entity.html | 26 - test/data/format/entity.kt | 4 - test/data/format/enumClass.kt | 4 - test/data/format/enumClass.md | 15 - test/data/format/enumClass.value.md | 8 - test/data/format/extensionFunctionParameter.kt | 1 - test/data/format/extensionFunctionParameter.md | 8 - test/data/format/extensions.class.md | 16 - test/data/format/extensions.kt | 19 - test/data/format/extensions.package.md | 11 - test/data/format/functionWithDefaultParameter.kt | 1 - test/data/format/functionWithDefaultParameter.md | 8 - test/data/format/htmlEscaping.html | 14 - test/data/format/htmlEscaping.kt | 4 - test/data/format/inheritedExtensions.kt | 11 - test/data/format/inheritedExtensions.md | 21 - test/data/format/inheritedMembers.kt | 12 - test/data/format/inheritedMembers.md | 38 - test/data/format/javaCodeInParam.java | 5 - test/data/format/javaCodeInParam.md | 21 - test/data/format/javaCodeLiteralTags.java | 6 - test/data/format/javaCodeLiteralTags.md | 23 - test/data/format/javaDeprecated.html | 14 - test/data/format/javaDeprecated.java | 5 - test/data/format/javaLinkTag.html | 36 - test/data/format/javaLinkTag.java | 6 - test/data/format/javaLinkTagWithLabel.html | 36 - test/data/format/javaLinkTagWithLabel.java | 6 - test/data/format/javaSeeTag.html | 38 - test/data/format/javaSeeTag.java | 6 - test/data/format/javaSpaceInAuthor.java | 5 - test/data/format/javaSpaceInAuthor.md | 19 - test/data/format/javaSupertype.html | 35 - test/data/format/javaSupertype.java | 8 - test/data/format/javadocHtml.java | 14 - test/data/format/javadocHtml.md | 27 - test/data/format/javadocOrderedList.java | 8 - test/data/format/javadocOrderedList.md | 20 - test/data/format/linkWithLabel.html | 37 - test/data/format/linkWithLabel.kt | 6 - test/data/format/nullability.kt | 5 - test/data/format/nullability.md | 20 - test/data/format/operatorOverloading.kt | 3 - test/data/format/operatorOverloading.md | 8 - test/data/format/orderedList.html | 30 - test/data/format/orderedList.kt | 8 - test/data/format/overloads.html | 23 - test/data/format/overloads.kt | 5 - test/data/format/overloadsWithDescription.html | 21 - test/data/format/overloadsWithDescription.kt | 15 - .../format/overloadsWithDifferentDescriptions.html | 30 - .../format/overloadsWithDifferentDescriptions.kt | 15 - test/data/format/overridingFunction.kt | 7 - test/data/format/overridingFunction.md | 9 - test/data/format/paramTag.kt | 6 - test/data/format/paramTag.md | 14 - test/data/format/parameterAnchor.html | 17 - test/data/format/parameterAnchor.kt | 6 - test/data/format/parenthesis.html | 14 - test/data/format/parenthesis.kt | 4 - test/data/format/propertyVar.kt | 1 - test/data/format/propertyVar.md | 8 - test/data/format/reifiedTypeParameter.kt | 3 - test/data/format/reifiedTypeParameter.md | 8 - test/data/format/see.html | 28 - test/data/format/see.kt | 12 - test/data/format/starProjection.kt | 3 - test/data/format/starProjection.md | 8 - test/data/format/summarizeSignatures.kt | 20 - test/data/format/summarizeSignatures.md | 23 - test/data/format/summarizeSignaturesProperty.kt | 20 - test/data/format/summarizeSignaturesProperty.md | 23 - test/data/format/throwsTag.kt | 5 - test/data/format/throwsTag.md | 13 - test/data/format/tripleBackticks.html | 16 - test/data/format/tripleBackticks.kt | 7 - test/data/format/typeLink.html | 24 - test/data/format/typeLink.kt | 5 - test/data/format/typeParameterBounds.kt | 6 - test/data/format/typeParameterBounds.md | 11 - test/data/format/typeParameterVariance.kt | 2 - test/data/format/typeParameterVariance.md | 14 - test/data/format/typeProjectionVariance.kt | 1 - test/data/format/typeProjectionVariance.md | 8 - test/data/format/varargsFunction.kt | 1 - test/data/format/varargsFunction.md | 8 - test/data/functions/annotatedFunction.kt | 2 - .../annotatedFunctionWithAnnotationParameters.kt | 7 - test/data/functions/function.kt | 5 - test/data/functions/functionWithAnnotatedParam.kt | 7 - .../data/functions/functionWithDefaultParameter.kt | 1 - test/data/functions/functionWithNoinlineParam.kt | 2 - .../functionWithNotDocumentedAnnotation.kt | 2 - test/data/functions/functionWithParams.kt | 8 - test/data/functions/functionWithReceiver.kt | 11 - test/data/functions/genericFunction.kt | 5 - .../functions/genericFunctionWithConstraints.kt | 6 - test/data/functions/inlineFunction.kt | 2 - test/data/java/annotatedAnnotation.java | 6 - test/data/java/arrayType.java | 5 - test/data/java/constructors.java | 5 - test/data/java/deprecation.java | 6 - test/data/java/enumValues.java | 3 - test/data/java/field.java | 4 - test/data/java/inheritorLinks.java | 7 - test/data/java/innerClass.java | 4 - test/data/java/javaLangObject.java | 3 - test/data/java/member.java | 11 - test/data/java/memberWithModifiers.java | 12 - test/data/java/staticMethod.java | 4 - test/data/java/superClass.java | 2 - test/data/java/typeParameter.java | 3 - test/data/java/varargs.java | 3 - test/data/links/linkToJDK.kt | 0 test/data/links/linkToMember.kt | 6 - test/data/links/linkToParam.kt | 5 - test/data/links/linkToQualifiedMember.kt | 6 - test/data/links/linkToSelf.kt | 6 - test/data/markdown/spec.txt | 6150 -------------------- test/data/packagedocs/stdlib.md | 11 - test/data/packages/dottedNamePackage.kt | 1 - test/data/packages/rootPackage.kt | 0 test/data/packages/simpleNamePackage.kt | 1 - test/data/packages/simpleNamePackage2.kt | 1 - test/data/properties/annotatedProperty.kt | 1 - test/data/properties/propertyOverride.kt | 7 - test/data/properties/propertyWithReceiver.kt | 2 - test/data/properties/valueProperty.kt | 1 - test/data/properties/valuePropertyWithGetter.kt | 2 - test/data/properties/variableProperty.kt | 1 - .../properties/variablePropertyWithAccessors.kt | 4 - 189 files changed, 8044 deletions(-) delete mode 100644 test/data/classes/annotatedClass.kt delete mode 100644 test/data/classes/annotatedClassWithAnnotationParameters.kt delete mode 100644 test/data/classes/classWithCompanionObject.kt delete mode 100644 test/data/classes/classWithConstructor.kt delete mode 100644 test/data/classes/classWithFunction.kt delete mode 100644 test/data/classes/classWithProperty.kt delete mode 100644 test/data/classes/companionObjectExtension.kt delete mode 100644 test/data/classes/dataClass.kt delete mode 100644 test/data/classes/emptyClass.kt delete mode 100644 test/data/classes/emptyObject.kt delete mode 100644 test/data/classes/genericClass.kt delete mode 100644 test/data/classes/indirectOverride.kt delete mode 100644 test/data/classes/innerClass.kt delete mode 100644 test/data/classes/javaAnnotationClass.kt delete mode 100644 test/data/classes/notOpenClass.kt delete mode 100644 test/data/classes/sealedClass.kt delete mode 100644 test/data/classes/secondaryConstructor.kt delete mode 100644 test/data/comments/directive.kt delete mode 100644 test/data/comments/emptyDoc.kt delete mode 100644 test/data/comments/emptyDocButComment.kt delete mode 100644 test/data/comments/emptySection.kt delete mode 100644 test/data/comments/multilineDoc.kt delete mode 100644 test/data/comments/multilineDocWithComment.kt delete mode 100644 test/data/comments/multilineSection.kt delete mode 100644 test/data/comments/oneLineDoc.kt delete mode 100644 test/data/comments/oneLineDocWithComment.kt delete mode 100644 test/data/comments/oneLineDocWithEmptyLine.kt delete mode 100644 test/data/comments/section1.kt delete mode 100644 test/data/comments/section2.kt delete mode 100644 test/data/format/accessor.kt delete mode 100644 test/data/format/accessor.md delete mode 100644 test/data/format/annotatedTypeParameter.kt delete mode 100644 test/data/format/annotatedTypeParameter.md delete mode 100644 test/data/format/annotationClass.kt delete mode 100644 test/data/format/annotationClass.md delete mode 100644 test/data/format/annotationParams.kt delete mode 100644 test/data/format/annotationParams.md delete mode 100644 test/data/format/annotations.kt delete mode 100644 test/data/format/annotations.md delete mode 100644 test/data/format/bracket.html delete mode 100644 test/data/format/bracket.kt delete mode 100644 test/data/format/brokenLink.html delete mode 100644 test/data/format/brokenLink.kt delete mode 100644 test/data/format/classWithCompanionObject.html delete mode 100644 test/data/format/classWithCompanionObject.kt delete mode 100644 test/data/format/classWithCompanionObject.md delete mode 100644 test/data/format/codeSpan.html delete mode 100644 test/data/format/codeSpan.kt delete mode 100644 test/data/format/companionObjectExtension.kt delete mode 100644 test/data/format/companionObjectExtension.md delete mode 100644 test/data/format/crossLanguage/kotlinExtendsJava/Bar.html delete mode 100644 test/data/format/crossLanguage/kotlinExtendsJava/Bar.kt delete mode 100644 test/data/format/crossLanguage/kotlinExtendsJava/test/Foo.java delete mode 100644 test/data/format/deprecated.class.html delete mode 100644 test/data/format/deprecated.kt delete mode 100644 test/data/format/deprecated.package.html delete mode 100644 test/data/format/emptyDescription.kt delete mode 100644 test/data/format/emptyDescription.md delete mode 100644 test/data/format/entity.html delete mode 100644 test/data/format/entity.kt delete mode 100644 test/data/format/enumClass.kt delete mode 100644 test/data/format/enumClass.md delete mode 100644 test/data/format/enumClass.value.md delete mode 100644 test/data/format/extensionFunctionParameter.kt delete mode 100644 test/data/format/extensionFunctionParameter.md delete mode 100644 test/data/format/extensions.class.md delete mode 100644 test/data/format/extensions.kt delete mode 100644 test/data/format/extensions.package.md delete mode 100644 test/data/format/functionWithDefaultParameter.kt delete mode 100644 test/data/format/functionWithDefaultParameter.md delete mode 100644 test/data/format/htmlEscaping.html delete mode 100644 test/data/format/htmlEscaping.kt delete mode 100644 test/data/format/inheritedExtensions.kt delete mode 100644 test/data/format/inheritedExtensions.md delete mode 100644 test/data/format/inheritedMembers.kt delete mode 100644 test/data/format/inheritedMembers.md delete mode 100644 test/data/format/javaCodeInParam.java delete mode 100644 test/data/format/javaCodeInParam.md delete mode 100644 test/data/format/javaCodeLiteralTags.java delete mode 100644 test/data/format/javaCodeLiteralTags.md delete mode 100644 test/data/format/javaDeprecated.html delete mode 100644 test/data/format/javaDeprecated.java delete mode 100644 test/data/format/javaLinkTag.html delete mode 100644 test/data/format/javaLinkTag.java delete mode 100644 test/data/format/javaLinkTagWithLabel.html delete mode 100644 test/data/format/javaLinkTagWithLabel.java delete mode 100644 test/data/format/javaSeeTag.html delete mode 100644 test/data/format/javaSeeTag.java delete mode 100644 test/data/format/javaSpaceInAuthor.java delete mode 100644 test/data/format/javaSpaceInAuthor.md delete mode 100644 test/data/format/javaSupertype.html delete mode 100644 test/data/format/javaSupertype.java delete mode 100644 test/data/format/javadocHtml.java delete mode 100644 test/data/format/javadocHtml.md delete mode 100644 test/data/format/javadocOrderedList.java delete mode 100644 test/data/format/javadocOrderedList.md delete mode 100644 test/data/format/linkWithLabel.html delete mode 100644 test/data/format/linkWithLabel.kt delete mode 100644 test/data/format/nullability.kt delete mode 100644 test/data/format/nullability.md delete mode 100644 test/data/format/operatorOverloading.kt delete mode 100644 test/data/format/operatorOverloading.md delete mode 100644 test/data/format/orderedList.html delete mode 100644 test/data/format/orderedList.kt delete mode 100644 test/data/format/overloads.html delete mode 100644 test/data/format/overloads.kt delete mode 100644 test/data/format/overloadsWithDescription.html delete mode 100644 test/data/format/overloadsWithDescription.kt delete mode 100644 test/data/format/overloadsWithDifferentDescriptions.html delete mode 100644 test/data/format/overloadsWithDifferentDescriptions.kt delete mode 100644 test/data/format/overridingFunction.kt delete mode 100644 test/data/format/overridingFunction.md delete mode 100644 test/data/format/paramTag.kt delete mode 100644 test/data/format/paramTag.md delete mode 100644 test/data/format/parameterAnchor.html delete mode 100644 test/data/format/parameterAnchor.kt delete mode 100644 test/data/format/parenthesis.html delete mode 100644 test/data/format/parenthesis.kt delete mode 100644 test/data/format/propertyVar.kt delete mode 100644 test/data/format/propertyVar.md delete mode 100644 test/data/format/reifiedTypeParameter.kt delete mode 100644 test/data/format/reifiedTypeParameter.md delete mode 100644 test/data/format/see.html delete mode 100644 test/data/format/see.kt delete mode 100644 test/data/format/starProjection.kt delete mode 100644 test/data/format/starProjection.md delete mode 100644 test/data/format/summarizeSignatures.kt delete mode 100644 test/data/format/summarizeSignatures.md delete mode 100644 test/data/format/summarizeSignaturesProperty.kt delete mode 100644 test/data/format/summarizeSignaturesProperty.md delete mode 100644 test/data/format/throwsTag.kt delete mode 100644 test/data/format/throwsTag.md delete mode 100644 test/data/format/tripleBackticks.html delete mode 100644 test/data/format/tripleBackticks.kt delete mode 100644 test/data/format/typeLink.html delete mode 100644 test/data/format/typeLink.kt delete mode 100644 test/data/format/typeParameterBounds.kt delete mode 100644 test/data/format/typeParameterBounds.md delete mode 100644 test/data/format/typeParameterVariance.kt delete mode 100644 test/data/format/typeParameterVariance.md delete mode 100644 test/data/format/typeProjectionVariance.kt delete mode 100644 test/data/format/typeProjectionVariance.md delete mode 100644 test/data/format/varargsFunction.kt delete mode 100644 test/data/format/varargsFunction.md delete mode 100644 test/data/functions/annotatedFunction.kt delete mode 100644 test/data/functions/annotatedFunctionWithAnnotationParameters.kt delete mode 100644 test/data/functions/function.kt delete mode 100644 test/data/functions/functionWithAnnotatedParam.kt delete mode 100644 test/data/functions/functionWithDefaultParameter.kt delete mode 100644 test/data/functions/functionWithNoinlineParam.kt delete mode 100644 test/data/functions/functionWithNotDocumentedAnnotation.kt delete mode 100644 test/data/functions/functionWithParams.kt delete mode 100644 test/data/functions/functionWithReceiver.kt delete mode 100644 test/data/functions/genericFunction.kt delete mode 100644 test/data/functions/genericFunctionWithConstraints.kt delete mode 100644 test/data/functions/inlineFunction.kt delete mode 100644 test/data/java/annotatedAnnotation.java delete mode 100644 test/data/java/arrayType.java delete mode 100644 test/data/java/constructors.java delete mode 100644 test/data/java/deprecation.java delete mode 100644 test/data/java/enumValues.java delete mode 100644 test/data/java/field.java delete mode 100644 test/data/java/inheritorLinks.java delete mode 100644 test/data/java/innerClass.java delete mode 100644 test/data/java/javaLangObject.java delete mode 100644 test/data/java/member.java delete mode 100644 test/data/java/memberWithModifiers.java delete mode 100644 test/data/java/staticMethod.java delete mode 100644 test/data/java/superClass.java delete mode 100644 test/data/java/typeParameter.java delete mode 100644 test/data/java/varargs.java delete mode 100644 test/data/links/linkToJDK.kt delete mode 100644 test/data/links/linkToMember.kt delete mode 100644 test/data/links/linkToParam.kt delete mode 100644 test/data/links/linkToQualifiedMember.kt delete mode 100644 test/data/links/linkToSelf.kt delete mode 100644 test/data/markdown/spec.txt delete mode 100644 test/data/packagedocs/stdlib.md delete mode 100644 test/data/packages/dottedNamePackage.kt delete mode 100644 test/data/packages/rootPackage.kt delete mode 100644 test/data/packages/simpleNamePackage.kt delete mode 100644 test/data/packages/simpleNamePackage2.kt delete mode 100644 test/data/properties/annotatedProperty.kt delete mode 100644 test/data/properties/propertyOverride.kt delete mode 100644 test/data/properties/propertyWithReceiver.kt delete mode 100644 test/data/properties/valueProperty.kt delete mode 100644 test/data/properties/valuePropertyWithGetter.kt delete mode 100644 test/data/properties/variableProperty.kt delete mode 100644 test/data/properties/variablePropertyWithAccessors.kt (limited to 'test/data') diff --git a/test/data/classes/annotatedClass.kt b/test/data/classes/annotatedClass.kt deleted file mode 100644 index 1b58f56c..00000000 --- a/test/data/classes/annotatedClass.kt +++ /dev/null @@ -1 +0,0 @@ -@Strictfp class Foo() {} diff --git a/test/data/classes/annotatedClassWithAnnotationParameters.kt b/test/data/classes/annotatedClassWithAnnotationParameters.kt deleted file mode 100644 index 930d6a62..00000000 --- a/test/data/classes/annotatedClassWithAnnotationParameters.kt +++ /dev/null @@ -1 +0,0 @@ -@Deprecated("should no longer be used") class Foo() {} diff --git a/test/data/classes/classWithCompanionObject.kt b/test/data/classes/classWithCompanionObject.kt deleted file mode 100644 index fdbd915d..00000000 --- a/test/data/classes/classWithCompanionObject.kt +++ /dev/null @@ -1,7 +0,0 @@ -class Klass() { - companion object { - val x = 1 - - fun foo() {} - } -} diff --git a/test/data/classes/classWithConstructor.kt b/test/data/classes/classWithConstructor.kt deleted file mode 100644 index 0751d570..00000000 --- a/test/data/classes/classWithConstructor.kt +++ /dev/null @@ -1 +0,0 @@ -class Klass(name: String) \ No newline at end of file diff --git a/test/data/classes/classWithFunction.kt b/test/data/classes/classWithFunction.kt deleted file mode 100644 index a981cfb6..00000000 --- a/test/data/classes/classWithFunction.kt +++ /dev/null @@ -1,4 +0,0 @@ -class Klass { - fun fn() { - } -} diff --git a/test/data/classes/classWithProperty.kt b/test/data/classes/classWithProperty.kt deleted file mode 100644 index 2a849572..00000000 --- a/test/data/classes/classWithProperty.kt +++ /dev/null @@ -1,3 +0,0 @@ -class Klass { - val name: String = "" -} \ No newline at end of file diff --git a/test/data/classes/companionObjectExtension.kt b/test/data/classes/companionObjectExtension.kt deleted file mode 100644 index 4b471376..00000000 --- a/test/data/classes/companionObjectExtension.kt +++ /dev/null @@ -1,10 +0,0 @@ -class Foo { - companion object Default { - } -} - - -/** - * The def - */ -val Foo.Default.x: Int get() = 1 diff --git a/test/data/classes/dataClass.kt b/test/data/classes/dataClass.kt deleted file mode 100644 index 62c6f0ec..00000000 --- a/test/data/classes/dataClass.kt +++ /dev/null @@ -1 +0,0 @@ -data class Foo() {} diff --git a/test/data/classes/emptyClass.kt b/test/data/classes/emptyClass.kt deleted file mode 100644 index abd20cc8..00000000 --- a/test/data/classes/emptyClass.kt +++ /dev/null @@ -1,3 +0,0 @@ -class Klass { - -} \ No newline at end of file diff --git a/test/data/classes/emptyObject.kt b/test/data/classes/emptyObject.kt deleted file mode 100644 index 4138bf31..00000000 --- a/test/data/classes/emptyObject.kt +++ /dev/null @@ -1,3 +0,0 @@ -object Obj { - -} \ No newline at end of file diff --git a/test/data/classes/genericClass.kt b/test/data/classes/genericClass.kt deleted file mode 100644 index db20ff7e..00000000 --- a/test/data/classes/genericClass.kt +++ /dev/null @@ -1,3 +0,0 @@ -class Klass { - -} \ No newline at end of file diff --git a/test/data/classes/indirectOverride.kt b/test/data/classes/indirectOverride.kt deleted file mode 100644 index 8d091b80..00000000 --- a/test/data/classes/indirectOverride.kt +++ /dev/null @@ -1,9 +0,0 @@ -abstract class C() { - abstract fun foo() -} - -abstract class D(): C() - -class E(): D() { - override fun foo() {} -} diff --git a/test/data/classes/innerClass.kt b/test/data/classes/innerClass.kt deleted file mode 100644 index 3c6e497d..00000000 --- a/test/data/classes/innerClass.kt +++ /dev/null @@ -1,5 +0,0 @@ -class C { - inner class D { - - } -} \ No newline at end of file diff --git a/test/data/classes/javaAnnotationClass.kt b/test/data/classes/javaAnnotationClass.kt deleted file mode 100644 index 95600147..00000000 --- a/test/data/classes/javaAnnotationClass.kt +++ /dev/null @@ -1,5 +0,0 @@ -import java.lang.annotation.Retention -import java.lang.annotation.RetentionPolicy - -@Retention(RetentionPolicy.SOURCE) -public annotation class throws() diff --git a/test/data/classes/notOpenClass.kt b/test/data/classes/notOpenClass.kt deleted file mode 100644 index edee2c1a..00000000 --- a/test/data/classes/notOpenClass.kt +++ /dev/null @@ -1,7 +0,0 @@ -open class C() { - open fun f() {} -} - -class D() : C() { - override fun f() {} -} diff --git a/test/data/classes/sealedClass.kt b/test/data/classes/sealedClass.kt deleted file mode 100644 index 93350393..00000000 --- a/test/data/classes/sealedClass.kt +++ /dev/null @@ -1 +0,0 @@ -sealed class Foo() {} diff --git a/test/data/classes/secondaryConstructor.kt b/test/data/classes/secondaryConstructor.kt deleted file mode 100644 index e5cb2557..00000000 --- a/test/data/classes/secondaryConstructor.kt +++ /dev/null @@ -1,5 +0,0 @@ -class C() { - /** This is a secondary constructor. */ - constructor(s: String): this() { - } -} diff --git a/test/data/comments/directive.kt b/test/data/comments/directive.kt deleted file mode 100644 index b27f5a48..00000000 --- a/test/data/comments/directive.kt +++ /dev/null @@ -1,35 +0,0 @@ -/** - * Summary - * - * @sample example1 - * @sample example2 - * @sample X.example3 - * @sample X.Y.example4 - */ -val property = "test" - -fun example1(node: String) = if (true) { - println(property) -} - -fun example2(node: String) { - if (true) { - println(property) - } -} - -class X { - fun example3(node: String) { - if (true) { - println(property) - } - } - - class Y { - fun example4(node: String) { - if (true) { - println(property) - } - } - } -} diff --git a/test/data/comments/emptyDoc.kt b/test/data/comments/emptyDoc.kt deleted file mode 100644 index b87cce57..00000000 --- a/test/data/comments/emptyDoc.kt +++ /dev/null @@ -1 +0,0 @@ -val property = "test" \ No newline at end of file diff --git a/test/data/comments/emptyDocButComment.kt b/test/data/comments/emptyDocButComment.kt deleted file mode 100644 index ceb24753..00000000 --- a/test/data/comments/emptyDocButComment.kt +++ /dev/null @@ -1,2 +0,0 @@ -/* comment */ -val property = "test" \ No newline at end of file diff --git a/test/data/comments/emptySection.kt b/test/data/comments/emptySection.kt deleted file mode 100644 index 47d6b1a5..00000000 --- a/test/data/comments/emptySection.kt +++ /dev/null @@ -1,6 +0,0 @@ - -/** - * Summary - * @one - */ -val property = "test" \ No newline at end of file diff --git a/test/data/comments/multilineDoc.kt b/test/data/comments/multilineDoc.kt deleted file mode 100644 index 31cfa3a7..00000000 --- a/test/data/comments/multilineDoc.kt +++ /dev/null @@ -1,7 +0,0 @@ -/** - * doc1 - * - * doc2 - * doc3 - */ -val property = "test" \ No newline at end of file diff --git a/test/data/comments/multilineDocWithComment.kt b/test/data/comments/multilineDocWithComment.kt deleted file mode 100644 index 88d22642..00000000 --- a/test/data/comments/multilineDocWithComment.kt +++ /dev/null @@ -1,8 +0,0 @@ -/** - * doc1 - * - * doc2 - * doc3 - */ -// comment -val property = "test" \ No newline at end of file diff --git a/test/data/comments/multilineSection.kt b/test/data/comments/multilineSection.kt deleted file mode 100644 index 6ef4df2c..00000000 --- a/test/data/comments/multilineSection.kt +++ /dev/null @@ -1,7 +0,0 @@ -/** - * Summary - * @one - * line one - * line two - */ -val property = "test" \ No newline at end of file diff --git a/test/data/comments/oneLineDoc.kt b/test/data/comments/oneLineDoc.kt deleted file mode 100644 index 92a40c67..00000000 --- a/test/data/comments/oneLineDoc.kt +++ /dev/null @@ -1,2 +0,0 @@ -/** doc */ -val property = "test" \ No newline at end of file diff --git a/test/data/comments/oneLineDocWithComment.kt b/test/data/comments/oneLineDocWithComment.kt deleted file mode 100644 index c8467933..00000000 --- a/test/data/comments/oneLineDocWithComment.kt +++ /dev/null @@ -1,3 +0,0 @@ -/** doc */ -// comment -val property = "test" \ No newline at end of file diff --git a/test/data/comments/oneLineDocWithEmptyLine.kt b/test/data/comments/oneLineDocWithEmptyLine.kt deleted file mode 100644 index e364c416..00000000 --- a/test/data/comments/oneLineDocWithEmptyLine.kt +++ /dev/null @@ -1,3 +0,0 @@ -/** doc */ - -val property = "test" \ No newline at end of file diff --git a/test/data/comments/section1.kt b/test/data/comments/section1.kt deleted file mode 100644 index 7c763b4c..00000000 --- a/test/data/comments/section1.kt +++ /dev/null @@ -1,5 +0,0 @@ -/** - * Summary - * @one section one - */ -val property = "test" \ No newline at end of file diff --git a/test/data/comments/section2.kt b/test/data/comments/section2.kt deleted file mode 100644 index e280793e..00000000 --- a/test/data/comments/section2.kt +++ /dev/null @@ -1,6 +0,0 @@ -/** - * Summary - * @one section one - * @two section two - */ -val property = "test" \ No newline at end of file diff --git a/test/data/format/accessor.kt b/test/data/format/accessor.kt deleted file mode 100644 index 5a4d1742..00000000 --- a/test/data/format/accessor.kt +++ /dev/null @@ -1,5 +0,0 @@ -class C() { - var x: String - /** The getter returns an empty string. */ get() = "" - /** The setter does nothing. */ set(value) { } -} diff --git a/test/data/format/accessor.md b/test/data/format/accessor.md deleted file mode 100644 index 8279f452..00000000 --- a/test/data/format/accessor.md +++ /dev/null @@ -1,18 +0,0 @@ -[test](test/index) / [C](test/-c/index) / [x](test/-c/x) - - -# x - -`var x: String` -**Getter** - -The getter returns an empty string. - - -**Setter** - -The setter does nothing. - - - - diff --git a/test/data/format/annotatedTypeParameter.kt b/test/data/format/annotatedTypeParameter.kt deleted file mode 100644 index cc3bfc1a..00000000 --- a/test/data/format/annotatedTypeParameter.kt +++ /dev/null @@ -1,2 +0,0 @@ -public fun containsAll(elements: Collection<@UnsafeVariance E>): @UnsafeVariance E { -} diff --git a/test/data/format/annotatedTypeParameter.md b/test/data/format/annotatedTypeParameter.md deleted file mode 100644 index 7d26a162..00000000 --- a/test/data/format/annotatedTypeParameter.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [containsAll](test/contains-all) - - -# containsAll - -`fun <E> containsAll(elements: Collection<@UnsafeVariance E>): @UnsafeVariance E` - - diff --git a/test/data/format/annotationClass.kt b/test/data/format/annotationClass.kt deleted file mode 100644 index 89d494fb..00000000 --- a/test/data/format/annotationClass.kt +++ /dev/null @@ -1 +0,0 @@ -annotation class fancy diff --git a/test/data/format/annotationClass.md b/test/data/format/annotationClass.md deleted file mode 100644 index 03548aa3..00000000 --- a/test/data/format/annotationClass.md +++ /dev/null @@ -1,14 +0,0 @@ -[test](test/index) / [fancy](test/fancy/index) - - -# fancy - -`annotation class fancy` - - - -### Constructors - - -| [<init>](test/fancy/-init-) | `fancy()` | - diff --git a/test/data/format/annotationParams.kt b/test/data/format/annotationParams.kt deleted file mode 100644 index f259a740..00000000 --- a/test/data/format/annotationParams.kt +++ /dev/null @@ -1 +0,0 @@ -@JvmName("FFF") fun f() {} diff --git a/test/data/format/annotationParams.md b/test/data/format/annotationParams.md deleted file mode 100644 index 8cdd6e96..00000000 --- a/test/data/format/annotationParams.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [f](test/f) - - -# f - -`@JvmName("FFF") fun f(): Unit` - - diff --git a/test/data/format/annotations.kt b/test/data/format/annotations.kt deleted file mode 100644 index 57f76249..00000000 --- a/test/data/format/annotations.kt +++ /dev/null @@ -1,6 +0,0 @@ -data class Foo { - inline fun bar(noinline notInlined: () -> Unit) { - } - - inline val x: Int -} diff --git a/test/data/format/annotations.md b/test/data/format/annotations.md deleted file mode 100644 index b898d55c..00000000 --- a/test/data/format/annotations.md +++ /dev/null @@ -1,26 +0,0 @@ -[test](test/index) / [Foo](test/-foo/index) - - -# Foo - -`data class Foo` - - - -### Constructors - - -| [<init>](test/-foo/-init-) | `Foo()` | - - -### Properties - - -| [x](test/-foo/x) | `val x: Int` | - - -### Functions - - -| [bar](test/-foo/bar) | `fun bar(notInlined: () -> Unit): Unit` | - diff --git a/test/data/format/bracket.html b/test/data/format/bracket.html deleted file mode 100644 index 5630073d..00000000 --- a/test/data/format/bracket.html +++ /dev/null @@ -1,14 +0,0 @@ - - -test / foo - - -test / foo
-
-

foo

-fun foo(): Unit
-

bar[]

-
-
- - diff --git a/test/data/format/bracket.kt b/test/data/format/bracket.kt deleted file mode 100644 index d41b0073..00000000 --- a/test/data/format/bracket.kt +++ /dev/null @@ -1,4 +0,0 @@ -/** - * bar[] - */ -fun foo() {} diff --git a/test/data/format/brokenLink.html b/test/data/format/brokenLink.html deleted file mode 100644 index 32135787..00000000 --- a/test/data/format/brokenLink.html +++ /dev/null @@ -1,14 +0,0 @@ - - -test / f - - -test / f
-
-

f

-fun f(): Unit
-

This references noSuchIdentifier.

-
-
- - diff --git a/test/data/format/brokenLink.kt b/test/data/format/brokenLink.kt deleted file mode 100644 index 268a986e..00000000 --- a/test/data/format/brokenLink.kt +++ /dev/null @@ -1,4 +0,0 @@ -/** - * This references [noSuchIdentifier]. - */ -fun f() { } diff --git a/test/data/format/classWithCompanionObject.html b/test/data/format/classWithCompanionObject.html deleted file mode 100644 index be9247ea..00000000 --- a/test/data/format/classWithCompanionObject.html +++ /dev/null @@ -1,46 +0,0 @@ - - -test / Klass - - -test / Klass
-
-

Klass

-class Klass
-
-
-

Constructors

- - - - - - - -
-<init> -Klass()
-

Companion Object Properties

- - - - - - - -
-x -val x: Int
-

Companion Object Functions

- - - - - - - -
-foo -fun foo(): Unit
- - diff --git a/test/data/format/classWithCompanionObject.kt b/test/data/format/classWithCompanionObject.kt deleted file mode 100644 index fdbd915d..00000000 --- a/test/data/format/classWithCompanionObject.kt +++ /dev/null @@ -1,7 +0,0 @@ -class Klass() { - companion object { - val x = 1 - - fun foo() {} - } -} diff --git a/test/data/format/classWithCompanionObject.md b/test/data/format/classWithCompanionObject.md deleted file mode 100644 index 9398c3d3..00000000 --- a/test/data/format/classWithCompanionObject.md +++ /dev/null @@ -1,26 +0,0 @@ -[test](test/index) / [Klass](test/-klass/index) - - -# Klass - -`class Klass` - - - -### Constructors - - -| [<init>](test/-klass/-init-) | `Klass()` | - - -### Companion Object Properties - - -| [x](test/-klass/x) | `val x: Int` | - - -### Companion Object Functions - - -| [foo](test/-klass/foo) | `fun foo(): Unit` | - diff --git a/test/data/format/codeSpan.html b/test/data/format/codeSpan.html deleted file mode 100644 index cc553043..00000000 --- a/test/data/format/codeSpan.html +++ /dev/null @@ -1,14 +0,0 @@ - - -test / foo - - -test / foo
-
-

foo

-fun foo(): Unit
-

This is a code span.

-
-
- - diff --git a/test/data/format/codeSpan.kt b/test/data/format/codeSpan.kt deleted file mode 100644 index 645f454a..00000000 --- a/test/data/format/codeSpan.kt +++ /dev/null @@ -1,4 +0,0 @@ -/** - * This is a `code span`. - */ -fun foo() {} \ No newline at end of file diff --git a/test/data/format/companionObjectExtension.kt b/test/data/format/companionObjectExtension.kt deleted file mode 100644 index f452de2c..00000000 --- a/test/data/format/companionObjectExtension.kt +++ /dev/null @@ -1,10 +0,0 @@ -class Foo { - companion object Default { - } -} - - -/** - * The default object property. - */ -val Foo.Default.x: Int get() = 1 diff --git a/test/data/format/companionObjectExtension.md b/test/data/format/companionObjectExtension.md deleted file mode 100644 index 271da5b0..00000000 --- a/test/data/format/companionObjectExtension.md +++ /dev/null @@ -1,23 +0,0 @@ -[test](test/index) / [Foo](test/-foo/index) - - -# Foo - -`class Foo` - - - -### Constructors - - -| [<init>](test/-foo/-init-) | `Foo()` | - - -### Companion Object Extension Properties - - -| [x](test/x) | `val Foo.Default.x: Int` -The default object property. - - | - diff --git a/test/data/format/crossLanguage/kotlinExtendsJava/Bar.html b/test/data/format/crossLanguage/kotlinExtendsJava/Bar.html deleted file mode 100644 index e7b139d8..00000000 --- a/test/data/format/crossLanguage/kotlinExtendsJava/Bar.html +++ /dev/null @@ -1,37 +0,0 @@ - - -test / test.Bar - - -test / test / Bar
-
-

Bar

-class Bar : Foo
-

See xyzzy

-
-
-

Constructors

- - - - - - - -
-<init> -Bar()

See xyzzy

-
-

Inherited Functions

- - - - - - - -
-xyzzy -open fun xyzzy(): Unit
- - diff --git a/test/data/format/crossLanguage/kotlinExtendsJava/Bar.kt b/test/data/format/crossLanguage/kotlinExtendsJava/Bar.kt deleted file mode 100644 index 102782f9..00000000 --- a/test/data/format/crossLanguage/kotlinExtendsJava/Bar.kt +++ /dev/null @@ -1,6 +0,0 @@ -package test - -/** - * See [xyzzy] - */ -class Bar(): Foo() diff --git a/test/data/format/crossLanguage/kotlinExtendsJava/test/Foo.java b/test/data/format/crossLanguage/kotlinExtendsJava/test/Foo.java deleted file mode 100644 index 7c143030..00000000 --- a/test/data/format/crossLanguage/kotlinExtendsJava/test/Foo.java +++ /dev/null @@ -1,6 +0,0 @@ -package test; - -public class Foo { - public void xyzzy() { - } -} diff --git a/test/data/format/deprecated.class.html b/test/data/format/deprecated.class.html deleted file mode 100644 index 69da63a1..00000000 --- a/test/data/format/deprecated.class.html +++ /dev/null @@ -1,41 +0,0 @@ - - - - -test / C
-
-

C

-class C
-Deprecated: This class sucks
-
-
-
-test / f
-
-

f

-fun f(): Unit
-Deprecated: This function sucks
-
-
-
-test / p
-
-

p

-val p: Int
-Deprecated: This property sucks
-
-
-
-

Constructors

- - - - - - - -
-<init> -C()
- - diff --git a/test/data/format/deprecated.kt b/test/data/format/deprecated.kt deleted file mode 100644 index 4fc568c2..00000000 --- a/test/data/format/deprecated.kt +++ /dev/null @@ -1,5 +0,0 @@ -@Deprecated("This class sucks") class C() { } - -@Deprecated("This function sucks") fun f() { } - -@Deprecated("This property sucks") val p: Int get() = 0 diff --git a/test/data/format/deprecated.package.html b/test/data/format/deprecated.package.html deleted file mode 100644 index dd80471c..00000000 --- a/test/data/format/deprecated.package.html +++ /dev/null @@ -1,43 +0,0 @@ - - -test / root package - - -test
-
-

Package

-

Types

- - - - - - - -
-C -class C
-

Properties

- - - - - - - -
-p -val p: Int
-

Functions

- - - - - - - -
-f -fun f(): Unit
- - diff --git a/test/data/format/emptyDescription.kt b/test/data/format/emptyDescription.kt deleted file mode 100644 index 3ed81dfa..00000000 --- a/test/data/format/emptyDescription.kt +++ /dev/null @@ -1,5 +0,0 @@ -/** - * Function fn - */ -fun fn() { -} \ No newline at end of file diff --git a/test/data/format/emptyDescription.md b/test/data/format/emptyDescription.md deleted file mode 100644 index e82e7228..00000000 --- a/test/data/format/emptyDescription.md +++ /dev/null @@ -1,11 +0,0 @@ -[test](test/index) / [fn](test/fn) - - -# fn - -`fun fn(): Unit` - -Function fn - - - diff --git a/test/data/format/entity.html b/test/data/format/entity.html deleted file mode 100644 index a939faad..00000000 --- a/test/data/format/entity.html +++ /dev/null @@ -1,26 +0,0 @@ - - -test / Bar - - -test / Bar
-
-

Bar

-class Bar
-

Copyright © JetBrains 2015 "

-
-
-

Constructors

- - - - - - - -
-<init> -Bar()

Copyright © JetBrains 2015 "

-
- - diff --git a/test/data/format/entity.kt b/test/data/format/entity.kt deleted file mode 100644 index 163d2ee6..00000000 --- a/test/data/format/entity.kt +++ /dev/null @@ -1,4 +0,0 @@ -/** - * Copyright © JetBrains 2015 " - */ -class Bar {} diff --git a/test/data/format/enumClass.kt b/test/data/format/enumClass.kt deleted file mode 100644 index c1af69d8..00000000 --- a/test/data/format/enumClass.kt +++ /dev/null @@ -1,4 +0,0 @@ -public enum class InlineOption { - LOCAL_CONTINUE_AND_BREAK, - ONLY_LOCAL_RETURN -} diff --git a/test/data/format/enumClass.md b/test/data/format/enumClass.md deleted file mode 100644 index 7a0e03ff..00000000 --- a/test/data/format/enumClass.md +++ /dev/null @@ -1,15 +0,0 @@ -[test](test/index) / [InlineOption](test/-inline-option/index) - - -# InlineOption - -`enum class InlineOption` - - - -### Enum Values - - -| [LOCAL_CONTINUE_AND_BREAK](test/-inline-option/-l-o-c-a-l_-c-o-n-t-i-n-u-e_-a-n-d_-b-r-e-a-k) | | -| [ONLY_LOCAL_RETURN](test/-inline-option/-o-n-l-y_-l-o-c-a-l_-r-e-t-u-r-n) | | - diff --git a/test/data/format/enumClass.value.md b/test/data/format/enumClass.value.md deleted file mode 100644 index bcb685d1..00000000 --- a/test/data/format/enumClass.value.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [InlineOption](test/-inline-option/index) / [LOCAL_CONTINUE_AND_BREAK](test/-inline-option/-l-o-c-a-l_-c-o-n-t-i-n-u-e_-a-n-d_-b-r-e-a-k) - - -# LOCAL_CONTINUE_AND_BREAK - -`LOCAL_CONTINUE_AND_BREAK` - - diff --git a/test/data/format/extensionFunctionParameter.kt b/test/data/format/extensionFunctionParameter.kt deleted file mode 100644 index bfb344b9..00000000 --- a/test/data/format/extensionFunctionParameter.kt +++ /dev/null @@ -1 +0,0 @@ -public inline fun T.apply(f: T.() -> Unit): T { f(); return this } diff --git a/test/data/format/extensionFunctionParameter.md b/test/data/format/extensionFunctionParameter.md deleted file mode 100644 index 6980912d..00000000 --- a/test/data/format/extensionFunctionParameter.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [apply](test/apply) - - -# apply - -`inline fun <T> T.apply(f: T.() -> Unit): T` - - diff --git a/test/data/format/extensions.class.md b/test/data/format/extensions.class.md deleted file mode 100644 index c66cdb01..00000000 --- a/test/data/format/extensions.class.md +++ /dev/null @@ -1,16 +0,0 @@ -[test](test/index) / [foo](test/foo/index) / [kotlin.String](test/foo/kotlin.-string/index) - - -### Extensions for kotlin.String - - -| [fn](test/foo/kotlin.-string/fn) | `fun String.fn(): Unit` -`fun String.fn(x: Int): Unit` -Function with receiver - - | -| [foobar](test/foo/kotlin.-string/foobar) | `val String.foobar: Int` -Property with receiver. - - | - diff --git a/test/data/format/extensions.kt b/test/data/format/extensions.kt deleted file mode 100644 index 6f2eff9d..00000000 --- a/test/data/format/extensions.kt +++ /dev/null @@ -1,19 +0,0 @@ -package foo - -/** - * Function with receiver - */ -fun String.fn() { -} - -/** - * Function with receiver - */ -fun String.fn(x: Int) { -} - -/** - * Property with receiver. - */ -val String.foobar: Int - get() = size() * 2 diff --git a/test/data/format/extensions.package.md b/test/data/format/extensions.package.md deleted file mode 100644 index 76ff3676..00000000 --- a/test/data/format/extensions.package.md +++ /dev/null @@ -1,11 +0,0 @@ -[test](test/index) / [foo](test/foo/index) - - -## Package foo - - -### Extensions for External Classes - - -| [kotlin.String](test/foo/kotlin.-string/index) | | - diff --git a/test/data/format/functionWithDefaultParameter.kt b/test/data/format/functionWithDefaultParameter.kt deleted file mode 100644 index 3a3a102f..00000000 --- a/test/data/format/functionWithDefaultParameter.kt +++ /dev/null @@ -1 +0,0 @@ -fun f(x: String = "") {} diff --git a/test/data/format/functionWithDefaultParameter.md b/test/data/format/functionWithDefaultParameter.md deleted file mode 100644 index 21e9eff7..00000000 --- a/test/data/format/functionWithDefaultParameter.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [f](test/f) - - -# f - -`fun f(x: String = ""): Unit` - - diff --git a/test/data/format/htmlEscaping.html b/test/data/format/htmlEscaping.html deleted file mode 100644 index a485c08f..00000000 --- a/test/data/format/htmlEscaping.html +++ /dev/null @@ -1,14 +0,0 @@ - - -test / x - - -test / x
-
-

x

-fun <T> x(): T?
-

Special characters: < is "less than", > is "greater than", & is "ampersand"

-
-
- - diff --git a/test/data/format/htmlEscaping.kt b/test/data/format/htmlEscaping.kt deleted file mode 100644 index 8778d8a5..00000000 --- a/test/data/format/htmlEscaping.kt +++ /dev/null @@ -1,4 +0,0 @@ -/** - * Special characters: < is "less than", > is "greater than", & is "ampersand" - */ -fun x(): T? = null diff --git a/test/data/format/inheritedExtensions.kt b/test/data/format/inheritedExtensions.kt deleted file mode 100644 index e38fe00d..00000000 --- a/test/data/format/inheritedExtensions.kt +++ /dev/null @@ -1,11 +0,0 @@ -open class Foo - -class Bar : Foo() - -fun Foo.first() { - -} - -fun Bar.second() { - -} diff --git a/test/data/format/inheritedExtensions.md b/test/data/format/inheritedExtensions.md deleted file mode 100644 index 79137eac..00000000 --- a/test/data/format/inheritedExtensions.md +++ /dev/null @@ -1,21 +0,0 @@ -[test](test/index) / [Bar](test/-bar/index) - - -# Bar - -`class Bar : [Foo](test/-foo/index)` - - - -### Constructors - - -| [<init>](test/-bar/-init-) | `Bar()` | - - -### Extension Functions - - -| [first](test/first) | `fun [Foo](test/-foo/index).first(): Unit` | -| [second](test/second) | `fun [Bar](test/-bar/index).second(): Unit` | - diff --git a/test/data/format/inheritedMembers.kt b/test/data/format/inheritedMembers.kt deleted file mode 100644 index 2d0c4ca1..00000000 --- a/test/data/format/inheritedMembers.kt +++ /dev/null @@ -1,12 +0,0 @@ -open class Foo { - fun first() { - } - - val firstProp: Int = 0 -} - -class Bar : Foo() { - fun second() - - val secondProp: Int = 1 -} diff --git a/test/data/format/inheritedMembers.md b/test/data/format/inheritedMembers.md deleted file mode 100644 index d58d3974..00000000 --- a/test/data/format/inheritedMembers.md +++ /dev/null @@ -1,38 +0,0 @@ -[test](test/index) / [Bar](test/-bar/index) - - -# Bar - -`class Bar : [Foo](test/-foo/index)` - - - -### Constructors - - -| [<init>](test/-bar/-init-) | `Bar()` | - - -### Properties - - -| [secondProp](test/-bar/second-prop) | `val secondProp: Int` | - - -### Inherited Properties - - -| [firstProp](test/-foo/first-prop) | `val firstProp: Int` | - - -### Functions - - -| [second](test/-bar/second) | `fun second(): Unit` | - - -### Inherited Functions - - -| [first](test/-foo/first) | `fun first(): Unit` | - diff --git a/test/data/format/javaCodeInParam.java b/test/data/format/javaCodeInParam.java deleted file mode 100644 index 73025fcc..00000000 --- a/test/data/format/javaCodeInParam.java +++ /dev/null @@ -1,5 +0,0 @@ -/** - * @param T this is {@code some code} and other text - */ -class C { -} diff --git a/test/data/format/javaCodeInParam.md b/test/data/format/javaCodeInParam.md deleted file mode 100644 index b1d2d871..00000000 --- a/test/data/format/javaCodeInParam.md +++ /dev/null @@ -1,21 +0,0 @@ -[test](test/index) / [C](test/-c/index) - - -# C - -`protected open class C<T : Any>` - - - - -### Parameters - -`T` - this is `some code` and other text - - - -### Constructors - - -| [<init>](test/-c/-init-) | `C()` | - diff --git a/test/data/format/javaCodeLiteralTags.java b/test/data/format/javaCodeLiteralTags.java deleted file mode 100644 index e71ddaa7..00000000 --- a/test/data/format/javaCodeLiteralTags.java +++ /dev/null @@ -1,6 +0,0 @@ -/** - *

{@code AC}

- *

{@literal AC}

- */ -class C { -} diff --git a/test/data/format/javaCodeLiteralTags.md b/test/data/format/javaCodeLiteralTags.md deleted file mode 100644 index 83c9cc33..00000000 --- a/test/data/format/javaCodeLiteralTags.md +++ /dev/null @@ -1,23 +0,0 @@ -[test](test/index) / [C](test/-c/index) - - -# C - -`protected open class C` - - -`A<B>C` - - -A<B>C - - - - - - -### Constructors - - -| [<init>](test/-c/-init-) | `C()` | - diff --git a/test/data/format/javaDeprecated.html b/test/data/format/javaDeprecated.html deleted file mode 100644 index 236c6490..00000000 --- a/test/data/format/javaDeprecated.html +++ /dev/null @@ -1,14 +0,0 @@ - - -test / Foo.foo - - -test / Foo / foo
-
-

foo

-open fun foo(): Unit
-Deprecated: use #bar instead

-
-
- - diff --git a/test/data/format/javaDeprecated.java b/test/data/format/javaDeprecated.java deleted file mode 100644 index 9694a444..00000000 --- a/test/data/format/javaDeprecated.java +++ /dev/null @@ -1,5 +0,0 @@ -class Foo { - /** @deprecated use {@link #bar} instead */ - public void foo() {} - public void bar() {} -} diff --git a/test/data/format/javaLinkTag.html b/test/data/format/javaLinkTag.html deleted file mode 100644 index 1b6921ab..00000000 --- a/test/data/format/javaLinkTag.html +++ /dev/null @@ -1,36 +0,0 @@ - - -test / Foo - - -test / Foo
-
-

Foo

-protected open class Foo
-

Call #bar() to do the job.

-
-
-

Constructors

- - - - - - - -
-<init> -Foo()
-

Functions

- - - - - - - -
-bar -open fun bar(): Unit
- - diff --git a/test/data/format/javaLinkTag.java b/test/data/format/javaLinkTag.java deleted file mode 100644 index 84f761c6..00000000 --- a/test/data/format/javaLinkTag.java +++ /dev/null @@ -1,6 +0,0 @@ -/** - * Call {@link #bar()} to do the job. - */ -class Foo { - public void bar() -} diff --git a/test/data/format/javaLinkTagWithLabel.html b/test/data/format/javaLinkTagWithLabel.html deleted file mode 100644 index aabfbc58..00000000 --- a/test/data/format/javaLinkTagWithLabel.html +++ /dev/null @@ -1,36 +0,0 @@ - - -test / Foo - - -test / Foo
-
-

Foo

-protected open class Foo
-

Call this wonderful method to do the job.

-
-
-

Constructors

- - - - - - - -
-<init> -Foo()
-

Functions

- - - - - - - -
-bar -open fun bar(): Unit
- - diff --git a/test/data/format/javaLinkTagWithLabel.java b/test/data/format/javaLinkTagWithLabel.java deleted file mode 100644 index 1db5ad70..00000000 --- a/test/data/format/javaLinkTagWithLabel.java +++ /dev/null @@ -1,6 +0,0 @@ -/** - * Call {@link #bar() this wonderful method} to do the job. - */ -class Foo { - public void bar() -} diff --git a/test/data/format/javaSeeTag.html b/test/data/format/javaSeeTag.html deleted file mode 100644 index a6813df3..00000000 --- a/test/data/format/javaSeeTag.html +++ /dev/null @@ -1,38 +0,0 @@ - - -test / Foo - - -test / Foo
-
-

Foo

-open class Foo
-

-See Also
-#bar
-
-
-

Constructors

- - - - - - - -
-<init> -Foo()
-

Functions

- - - - - - - -
-bar -open fun bar(): Unit
- - diff --git a/test/data/format/javaSeeTag.java b/test/data/format/javaSeeTag.java deleted file mode 100644 index 94a24606..00000000 --- a/test/data/format/javaSeeTag.java +++ /dev/null @@ -1,6 +0,0 @@ -/** - * @see #bar - */ -public class Foo { - public void bar() {} -} \ No newline at end of file diff --git a/test/data/format/javaSpaceInAuthor.java b/test/data/format/javaSpaceInAuthor.java deleted file mode 100644 index f980ae07..00000000 --- a/test/data/format/javaSpaceInAuthor.java +++ /dev/null @@ -1,5 +0,0 @@ -/** - * @author Dmitry Jemerov - */ -class C { -} \ No newline at end of file diff --git a/test/data/format/javaSpaceInAuthor.md b/test/data/format/javaSpaceInAuthor.md deleted file mode 100644 index 4d19ed01..00000000 --- a/test/data/format/javaSpaceInAuthor.md +++ /dev/null @@ -1,19 +0,0 @@ -[test](test/index) / [C](test/-c/index) - - -# C - -`protected open class C` - - - -**Author** -Dmitry Jemerov - - - -### Constructors - - -| [<init>](test/-c/-init-) | `C()` | - diff --git a/test/data/format/javaSupertype.html b/test/data/format/javaSupertype.html deleted file mode 100644 index 4c847281..00000000 --- a/test/data/format/javaSupertype.html +++ /dev/null @@ -1,35 +0,0 @@ - - -test / C.Bar - - -test / C / Bar
-
-

Bar

-open class Bar : Foo
-
-
-

Constructors

- - - - - - - -
-<init> -Bar()
-

Functions

- - - - - - - -
-returnFoo -open fun returnFoo(foo: Foo): Foo
- - diff --git a/test/data/format/javaSupertype.java b/test/data/format/javaSupertype.java deleted file mode 100644 index b3142ff6..00000000 --- a/test/data/format/javaSupertype.java +++ /dev/null @@ -1,8 +0,0 @@ -class C { - public static class Foo { - } - - public static class Bar extends Foo { - public Foo returnFoo(Foo foo) { return foo; } - } -} diff --git a/test/data/format/javadocHtml.java b/test/data/format/javadocHtml.java deleted file mode 100644 index 622116b2..00000000 --- a/test/data/format/javadocHtml.java +++ /dev/null @@ -1,14 +0,0 @@ -/** - * Bold - * Strong - * Italic - * Emphasized - *

Paragraph

- * Strikethrough - * Deleted - * Code - * 
Block code
- *
  • List Item
- */ -public class C { -} diff --git a/test/data/format/javadocHtml.md b/test/data/format/javadocHtml.md deleted file mode 100644 index db71cc3b..00000000 --- a/test/data/format/javadocHtml.md +++ /dev/null @@ -1,27 +0,0 @@ -[test](test/index) / [C](test/-c/index) - - -# C - -`open class C` - -**Bold** **Strong** *Italic* *Emphasized* -Paragraph - - ~~Strikethrough~~ ~~Deleted~~ `Code` -``` -Block code -``` - - * List Item - - - - - - -### Constructors - - -| [<init>](test/-c/-init-) | `C()` | - diff --git a/test/data/format/javadocOrderedList.java b/test/data/format/javadocOrderedList.java deleted file mode 100644 index c32d9032..00000000 --- a/test/data/format/javadocOrderedList.java +++ /dev/null @@ -1,8 +0,0 @@ -/** - *
    - *
  1. Rinse
    2. - *
  2. Repeat
    3. - *
- */ -public class Bar { -} diff --git a/test/data/format/javadocOrderedList.md b/test/data/format/javadocOrderedList.md deleted file mode 100644 index 02a3c095..00000000 --- a/test/data/format/javadocOrderedList.md +++ /dev/null @@ -1,20 +0,0 @@ -[test](test/index) / [Bar](test/-bar/index) - - -# Bar - -`open class Bar` - - 1. Rinse - 1. Repeat - - - - - - -### Constructors - - -| [<init>](test/-bar/-init-) | `Bar()` | - diff --git a/test/data/format/linkWithLabel.html b/test/data/format/linkWithLabel.html deleted file mode 100644 index 75769ffd..00000000 --- a/test/data/format/linkWithLabel.html +++ /dev/null @@ -1,37 +0,0 @@ - - -test / Bar - - -test / Bar
-
-

Bar

-class Bar
-

Use this method for best results.

-
-
-

Constructors

- - - - - - - -
-<init> -Bar()

Use this method for best results.

-
-

Functions

- - - - - - - -
-foo -fun foo(): Unit
- - diff --git a/test/data/format/linkWithLabel.kt b/test/data/format/linkWithLabel.kt deleted file mode 100644 index 4a85c505..00000000 --- a/test/data/format/linkWithLabel.kt +++ /dev/null @@ -1,6 +0,0 @@ -/** - * Use [this method][Bar.foo] for best results. - */ -class Bar { - fun foo() {} -} diff --git a/test/data/format/nullability.kt b/test/data/format/nullability.kt deleted file mode 100644 index d1d4545b..00000000 --- a/test/data/format/nullability.kt +++ /dev/null @@ -1,5 +0,0 @@ -class C { - fun foo(): Comparable? { - return null - } -} diff --git a/test/data/format/nullability.md b/test/data/format/nullability.md deleted file mode 100644 index ee50a0a5..00000000 --- a/test/data/format/nullability.md +++ /dev/null @@ -1,20 +0,0 @@ -[test](test/index) / [C](test/-c/index) - - -# C - -`class C<T>` - - - -### Constructors - - -| [<init>](test/-c/-init-) | `C()` | - - -### Functions - - -| [foo](test/-c/foo) | `fun foo(): Comparable<T>?` | - diff --git a/test/data/format/operatorOverloading.kt b/test/data/format/operatorOverloading.kt deleted file mode 100644 index 6fe78e45..00000000 --- a/test/data/format/operatorOverloading.kt +++ /dev/null @@ -1,3 +0,0 @@ -class C { - fun plus(other: C): C -} diff --git a/test/data/format/operatorOverloading.md b/test/data/format/operatorOverloading.md deleted file mode 100644 index 05fe3206..00000000 --- a/test/data/format/operatorOverloading.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [C](test/-c/index) / [plus](test/-c/plus) - - -# plus - -`fun plus(other: [C](test/-c/index)): [C](test/-c/index)` - - diff --git a/test/data/format/orderedList.html b/test/data/format/orderedList.html deleted file mode 100644 index 9917568f..00000000 --- a/test/data/format/orderedList.html +++ /dev/null @@ -1,30 +0,0 @@ - - -test / Bar - - -test / Bar
-
-

Bar

-class Bar
-

Usage instructions:

-

  1. Rinse

    -

  2. Repeat

    -

-
-
-
-

Constructors

- - - - - - - -
-<init> -Bar()

Usage instructions:

-
- - diff --git a/test/data/format/orderedList.kt b/test/data/format/orderedList.kt deleted file mode 100644 index 03681c7a..00000000 --- a/test/data/format/orderedList.kt +++ /dev/null @@ -1,8 +0,0 @@ -/** - * Usage instructions: - * - * 1. Rinse - * 1. Repeat - */ -class Bar { -} diff --git a/test/data/format/overloads.html b/test/data/format/overloads.html deleted file mode 100644 index 752f3989..00000000 --- a/test/data/format/overloads.html +++ /dev/null @@ -1,23 +0,0 @@ - - -test / root package - - -test
-
-

Package

-

Functions

- - - - - - - -
-f -fun f(x: Int): Unit
-fun f(x: String): Unit

Performs an action on x.

-
- - diff --git a/test/data/format/overloads.kt b/test/data/format/overloads.kt deleted file mode 100644 index dcd2d097..00000000 --- a/test/data/format/overloads.kt +++ /dev/null @@ -1,5 +0,0 @@ -/** Performs an action on x. */ -fun f(x: Int) { } - -/** Performs an action on x. */ -fun f(x: String) { } diff --git a/test/data/format/overloadsWithDescription.html b/test/data/format/overloadsWithDescription.html deleted file mode 100644 index a0efb472..00000000 --- a/test/data/format/overloadsWithDescription.html +++ /dev/null @@ -1,21 +0,0 @@ - - -test / f - - -test / f
-
-

f

-fun f(x: Int): Unit
-fun f(x: String): Unit
-

Performs an action on x.

-

This is a long description.

-
-
-

Parameters

- -x - the value to perform the action on.
-
-
- - diff --git a/test/data/format/overloadsWithDescription.kt b/test/data/format/overloadsWithDescription.kt deleted file mode 100644 index 740e642f..00000000 --- a/test/data/format/overloadsWithDescription.kt +++ /dev/null @@ -1,15 +0,0 @@ -/** - * Performs an action on [x]. - * - * This is a long description. - * @param x the value to perform the action on. - */ -fun f(x: Int) { } - -/** - * Performs an action on [x]. - * - * This is a long description. - * @param x the value to perform the action on. - */ -fun f(x: String) { } diff --git a/test/data/format/overloadsWithDifferentDescriptions.html b/test/data/format/overloadsWithDifferentDescriptions.html deleted file mode 100644 index 30a37e75..00000000 --- a/test/data/format/overloadsWithDifferentDescriptions.html +++ /dev/null @@ -1,30 +0,0 @@ - - -test / f - - -test / f
-
-

f

-fun f(x: Int): Unit
-

Performs an action on x.

-

This is a long description.

-
-
-

Parameters

- -x - the int value to perform the action on.
-
-
-fun f(x: String): Unit
-

Performs an action on x.

-

This is a long description.

-
-
-

Parameters

- -x - the string value to perform the action on.
-
-
- - diff --git a/test/data/format/overloadsWithDifferentDescriptions.kt b/test/data/format/overloadsWithDifferentDescriptions.kt deleted file mode 100644 index ad3169b0..00000000 --- a/test/data/format/overloadsWithDifferentDescriptions.kt +++ /dev/null @@ -1,15 +0,0 @@ -/** - * Performs an action on x. - * - * This is a long description. - * @param x the int value to perform the action on. - */ -fun f(x: Int) { } - -/** - * Performs an action on x. - * - * This is a long description. - * @param x the string value to perform the action on. - */ -fun f(x: String) { } diff --git a/test/data/format/overridingFunction.kt b/test/data/format/overridingFunction.kt deleted file mode 100644 index d7329489..00000000 --- a/test/data/format/overridingFunction.kt +++ /dev/null @@ -1,7 +0,0 @@ -open class C() { - open fun f() {} -} - -class D(): C() { - override fun f() {} -} diff --git a/test/data/format/overridingFunction.md b/test/data/format/overridingFunction.md deleted file mode 100644 index 2c898b9c..00000000 --- a/test/data/format/overridingFunction.md +++ /dev/null @@ -1,9 +0,0 @@ -[test](test/index) / [D](test/-d/index) / [f](test/-d/f) - - -# f - -`fun f(): Unit` -Overrides [C.f](test/-c/f) - - diff --git a/test/data/format/paramTag.kt b/test/data/format/paramTag.kt deleted file mode 100644 index 47e471f5..00000000 --- a/test/data/format/paramTag.kt +++ /dev/null @@ -1,6 +0,0 @@ -/** - * @param x A string - * @param y A number with a really long description that spans multiple lines and goes - * on and on and is very interesting to read - */ -fun f(x: String, y: Int) {} diff --git a/test/data/format/paramTag.md b/test/data/format/paramTag.md deleted file mode 100644 index 882083fe..00000000 --- a/test/data/format/paramTag.md +++ /dev/null @@ -1,14 +0,0 @@ -[test](test/index) / [f](test/f) - - -# f - -`fun f(x: String, y: Int): Unit` - -### Parameters - -`x` - A string -`y` - A number with a really long description that spans multiple lines and goes -on and on and is very interesting to read - - diff --git a/test/data/format/parameterAnchor.html b/test/data/format/parameterAnchor.html deleted file mode 100644 index c5920fb7..00000000 --- a/test/data/format/parameterAnchor.html +++ /dev/null @@ -1,17 +0,0 @@ - - -test / processFiles - - -test / processFiles
-
-

processFiles

-fun <T> processFiles(processor: () -> T): List<T>
-

Runs processor for each file and collects its results into single list

-

Parameters

- -processor - function to receive context for symbol resolution and file for processing
-
-
- - diff --git a/test/data/format/parameterAnchor.kt b/test/data/format/parameterAnchor.kt deleted file mode 100644 index ae36ee4c..00000000 --- a/test/data/format/parameterAnchor.kt +++ /dev/null @@ -1,6 +0,0 @@ -/** - * Runs [processor] for each file and collects its results into single list - * @param processor function to receive context for symbol resolution and file for processing - */ -public fun processFiles(processor: () -> T): List { -} diff --git a/test/data/format/parenthesis.html b/test/data/format/parenthesis.html deleted file mode 100644 index c36b311b..00000000 --- a/test/data/format/parenthesis.html +++ /dev/null @@ -1,14 +0,0 @@ - - -test / foo - - -test / foo
-
-

foo

-fun foo(): Unit
-

foo (bar)

-
-
- - diff --git a/test/data/format/parenthesis.kt b/test/data/format/parenthesis.kt deleted file mode 100644 index b906f64a..00000000 --- a/test/data/format/parenthesis.kt +++ /dev/null @@ -1,4 +0,0 @@ -/** - * foo (bar) - */ -fun foo() {} diff --git a/test/data/format/propertyVar.kt b/test/data/format/propertyVar.kt deleted file mode 100644 index 88be1a7a..00000000 --- a/test/data/format/propertyVar.kt +++ /dev/null @@ -1 +0,0 @@ -var x = 1 \ No newline at end of file diff --git a/test/data/format/propertyVar.md b/test/data/format/propertyVar.md deleted file mode 100644 index f2110992..00000000 --- a/test/data/format/propertyVar.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [x](test/x) - - -# x - -`var x: Int` - - diff --git a/test/data/format/reifiedTypeParameter.kt b/test/data/format/reifiedTypeParameter.kt deleted file mode 100644 index 00fa1dc9..00000000 --- a/test/data/format/reifiedTypeParameter.kt +++ /dev/null @@ -1,3 +0,0 @@ -inline fun f() { - -} diff --git a/test/data/format/reifiedTypeParameter.md b/test/data/format/reifiedTypeParameter.md deleted file mode 100644 index 2e96018e..00000000 --- a/test/data/format/reifiedTypeParameter.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [f](test/f) - - -# f - -`inline fun <reified T> f(): Unit` - - diff --git a/test/data/format/see.html b/test/data/format/see.html deleted file mode 100644 index b3ffb74b..00000000 --- a/test/data/format/see.html +++ /dev/null @@ -1,28 +0,0 @@ - - - - -test / quux
-
-

quux

-fun quux(): Unit
-See Also
-

foo

-

bar

-
-
-
-test / foo
-
-

foo

-fun foo(): Unit
-
-
-test / bar
-
-

bar

-fun bar(): Unit
-
-
- - diff --git a/test/data/format/see.kt b/test/data/format/see.kt deleted file mode 100644 index a0b153b0..00000000 --- a/test/data/format/see.kt +++ /dev/null @@ -1,12 +0,0 @@ -/** - * @see foo - * @see bar - */ -fun quux() { -} - -fun foo() { -} - -fun bar() { -} \ No newline at end of file diff --git a/test/data/format/starProjection.kt b/test/data/format/starProjection.kt deleted file mode 100644 index 48d53e47..00000000 --- a/test/data/format/starProjection.kt +++ /dev/null @@ -1,3 +0,0 @@ -public fun Iterable<*>.containsFoo(element: Any?): Boolean { - return false -} diff --git a/test/data/format/starProjection.md b/test/data/format/starProjection.md deleted file mode 100644 index c9be2f58..00000000 --- a/test/data/format/starProjection.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [kotlin.Iterable](test/kotlin.-iterable/index) - - -### Extensions for kotlin.Iterable - - -| [containsFoo](test/kotlin.-iterable/contains-foo) | `fun Iterable<*>.containsFoo(element: Any?): Boolean` | - diff --git a/test/data/format/summarizeSignatures.kt b/test/data/format/summarizeSignatures.kt deleted file mode 100644 index 1d875a50..00000000 --- a/test/data/format/summarizeSignatures.kt +++ /dev/null @@ -1,20 +0,0 @@ -package kotlin - -class Array -class IntArray -class CharArray - -/** - * Returns true if foo. - */ -fun IntArray.foo(predicate: (Int) -> Boolean): Boolean = false - -/** - * Returns true if foo. - */ -fun CharArray.foo(predicate: (Char) -> Boolean): Boolean = false - -/** - * Returns true if foo. - */ -fun Array.foo(predicate: (T) -> Boolean): Boolean = false diff --git a/test/data/format/summarizeSignatures.md b/test/data/format/summarizeSignatures.md deleted file mode 100644 index b1707f40..00000000 --- a/test/data/format/summarizeSignatures.md +++ /dev/null @@ -1,23 +0,0 @@ -[test](test/index) / [kotlin](test/kotlin/index) - - -## Package kotlin - - -### Types - - -| [Array](test/kotlin/-array/index) | `class Array<T>` | -| [CharArray](test/kotlin/-char-array/index) | `class CharArray` | -| [IntArray](test/kotlin/-int-array/index) | `class IntArray` | - - -### Functions - - -| [foo](test/kotlin/foo) | `fun <T> any_array<T>.foo(predicate: (T) -> Boolean): Boolean` - -Returns true if foo. - - | - diff --git a/test/data/format/summarizeSignaturesProperty.kt b/test/data/format/summarizeSignaturesProperty.kt deleted file mode 100644 index fbbdd328..00000000 --- a/test/data/format/summarizeSignaturesProperty.kt +++ /dev/null @@ -1,20 +0,0 @@ -package kotlin - -class Array -class IntArray -class CharArray - -/** - * Returns true if foo. - */ -val IntArray.foo: Int = 0 - -/** - * Returns true if foo. - */ -val CharArray.foo: Int = 0 - -/** - * Returns true if foo. - */ -val Array.foo: Int = 0 diff --git a/test/data/format/summarizeSignaturesProperty.md b/test/data/format/summarizeSignaturesProperty.md deleted file mode 100644 index 9646b0f1..00000000 --- a/test/data/format/summarizeSignaturesProperty.md +++ /dev/null @@ -1,23 +0,0 @@ -[test](test/index) / [kotlin](test/kotlin/index) - - -## Package kotlin - - -### Types - - -| [Array](test/kotlin/-array/index) | `class Array<T>` | -| [CharArray](test/kotlin/-char-array/index) | `class CharArray` | -| [IntArray](test/kotlin/-int-array/index) | `class IntArray` | - - -### Properties - - -| [foo](test/kotlin/foo) | `val <T> any_array<T>.foo: Int` - -Returns true if foo. - - | - diff --git a/test/data/format/throwsTag.kt b/test/data/format/throwsTag.kt deleted file mode 100644 index 29a9c3f7..00000000 --- a/test/data/format/throwsTag.kt +++ /dev/null @@ -1,5 +0,0 @@ -/** - * @throws IllegalArgumentException on Mondays - * @exception NullPointerException on Tuesdays - */ -fun f() {} diff --git a/test/data/format/throwsTag.md b/test/data/format/throwsTag.md deleted file mode 100644 index d0a4e610..00000000 --- a/test/data/format/throwsTag.md +++ /dev/null @@ -1,13 +0,0 @@ -[test](test/index) / [f](test/f) - - -# f - -`fun f(): Unit` - -### Exceptions - -`IllegalArgumentException` - on Mondays -`NullPointerException` - on Tuesdays - - diff --git a/test/data/format/tripleBackticks.html b/test/data/format/tripleBackticks.html deleted file mode 100644 index 13954985..00000000 --- a/test/data/format/tripleBackticks.html +++ /dev/null @@ -1,16 +0,0 @@ - - -test / f - - -test / f
-
-

f

-fun f(): Unit
-

Description

-
code sample

-
-
-
- - diff --git a/test/data/format/tripleBackticks.kt b/test/data/format/tripleBackticks.kt deleted file mode 100644 index 54dfa6d5..00000000 --- a/test/data/format/tripleBackticks.kt +++ /dev/null @@ -1,7 +0,0 @@ -/** - * Description - * ``` - * code sample - * ``` - */ -fun f() {} diff --git a/test/data/format/typeLink.html b/test/data/format/typeLink.html deleted file mode 100644 index ff99090a..00000000 --- a/test/data/format/typeLink.html +++ /dev/null @@ -1,24 +0,0 @@ - - -test / Bar - - -test / Bar
-
-

Bar

-class Bar : Foo
-
-
-

Constructors

- - - - - - - -
-<init> -Bar()
- - diff --git a/test/data/format/typeLink.kt b/test/data/format/typeLink.kt deleted file mode 100644 index 966e020e..00000000 --- a/test/data/format/typeLink.kt +++ /dev/null @@ -1,5 +0,0 @@ -class Foo() { -} - -class Bar(): Foo { -} diff --git a/test/data/format/typeParameterBounds.kt b/test/data/format/typeParameterBounds.kt deleted file mode 100644 index 5f22f8c5..00000000 --- a/test/data/format/typeParameterBounds.kt +++ /dev/null @@ -1,6 +0,0 @@ - -/** - * generic function - */ -public fun generic() { -} \ No newline at end of file diff --git a/test/data/format/typeParameterBounds.md b/test/data/format/typeParameterBounds.md deleted file mode 100644 index fe597878..00000000 --- a/test/data/format/typeParameterBounds.md +++ /dev/null @@ -1,11 +0,0 @@ -[test](test/index) / [generic](test/generic) - - -# generic - -`fun <T : R, R> generic(): Unit` - -generic function - - - diff --git a/test/data/format/typeParameterVariance.kt b/test/data/format/typeParameterVariance.kt deleted file mode 100644 index 28b29f4b..00000000 --- a/test/data/format/typeParameterVariance.kt +++ /dev/null @@ -1,2 +0,0 @@ -class Foo { -} diff --git a/test/data/format/typeParameterVariance.md b/test/data/format/typeParameterVariance.md deleted file mode 100644 index c0bfa6de..00000000 --- a/test/data/format/typeParameterVariance.md +++ /dev/null @@ -1,14 +0,0 @@ -[test](test/index) / [Foo](test/-foo/index) - - -# Foo - -`class Foo<out T>` - - - -### Constructors - - -| [<init>](test/-foo/-init-) | `Foo()` | - diff --git a/test/data/format/typeProjectionVariance.kt b/test/data/format/typeProjectionVariance.kt deleted file mode 100644 index 85ee344d..00000000 --- a/test/data/format/typeProjectionVariance.kt +++ /dev/null @@ -1 +0,0 @@ -fun Array.foo() {} diff --git a/test/data/format/typeProjectionVariance.md b/test/data/format/typeProjectionVariance.md deleted file mode 100644 index 7aa34593..00000000 --- a/test/data/format/typeProjectionVariance.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [kotlin.Array](test/kotlin.-array/index) - - -### Extensions for kotlin.Array - - -| [foo](test/kotlin.-array/foo) | `fun <T> Array<out T>.foo(): Unit` | - diff --git a/test/data/format/varargsFunction.kt b/test/data/format/varargsFunction.kt deleted file mode 100644 index deea127b..00000000 --- a/test/data/format/varargsFunction.kt +++ /dev/null @@ -1 +0,0 @@ -fun f(vararg s: String) {} diff --git a/test/data/format/varargsFunction.md b/test/data/format/varargsFunction.md deleted file mode 100644 index 723437aa..00000000 --- a/test/data/format/varargsFunction.md +++ /dev/null @@ -1,8 +0,0 @@ -[test](test/index) / [f](test/f) - - -# f - -`fun f(vararg s: String): Unit` - - diff --git a/test/data/functions/annotatedFunction.kt b/test/data/functions/annotatedFunction.kt deleted file mode 100644 index f7abbf6c..00000000 --- a/test/data/functions/annotatedFunction.kt +++ /dev/null @@ -1,2 +0,0 @@ -@Strictfp fun f() { -} diff --git a/test/data/functions/annotatedFunctionWithAnnotationParameters.kt b/test/data/functions/annotatedFunctionWithAnnotationParameters.kt deleted file mode 100644 index e559713a..00000000 --- a/test/data/functions/annotatedFunctionWithAnnotationParameters.kt +++ /dev/null @@ -1,7 +0,0 @@ -@Target(AnnotationTarget.VALUE_PARAMETER) -@Retention(AnnotationRetention.SOURCE) -@MustBeDocumented -public annotation class Fancy(val size: Int) - - -@Fancy(1) fun f() {} diff --git a/test/data/functions/function.kt b/test/data/functions/function.kt deleted file mode 100644 index 3ed81dfa..00000000 --- a/test/data/functions/function.kt +++ /dev/null @@ -1,5 +0,0 @@ -/** - * Function fn - */ -fun fn() { -} \ No newline at end of file diff --git a/test/data/functions/functionWithAnnotatedParam.kt b/test/data/functions/functionWithAnnotatedParam.kt deleted file mode 100644 index f858e671..00000000 --- a/test/data/functions/functionWithAnnotatedParam.kt +++ /dev/null @@ -1,7 +0,0 @@ -@Target(AnnotationTarget.VALUE_PARAMETER) -@Retention(AnnotationRetention.SOURCE) -@MustBeDocumented -public annotation class Fancy - -fun function(@Fancy notInlined: () -> Unit) { -} diff --git a/test/data/functions/functionWithDefaultParameter.kt b/test/data/functions/functionWithDefaultParameter.kt deleted file mode 100644 index 3a3a102f..00000000 --- a/test/data/functions/functionWithDefaultParameter.kt +++ /dev/null @@ -1 +0,0 @@ -fun f(x: String = "") {} diff --git a/test/data/functions/functionWithNoinlineParam.kt b/test/data/functions/functionWithNoinlineParam.kt deleted file mode 100644 index 640bec83..00000000 --- a/test/data/functions/functionWithNoinlineParam.kt +++ /dev/null @@ -1,2 +0,0 @@ -fun function(noinline notInlined: () -> Unit) { -} diff --git a/test/data/functions/functionWithNotDocumentedAnnotation.kt b/test/data/functions/functionWithNotDocumentedAnnotation.kt deleted file mode 100644 index 3c7e2ff9..00000000 --- a/test/data/functions/functionWithNotDocumentedAnnotation.kt +++ /dev/null @@ -1,2 +0,0 @@ -@Suppress("FOO") fun f() { -} diff --git a/test/data/functions/functionWithParams.kt b/test/data/functions/functionWithParams.kt deleted file mode 100644 index 85c49368..00000000 --- a/test/data/functions/functionWithParams.kt +++ /dev/null @@ -1,8 +0,0 @@ -/** - * Multiline - * - * Function - * Documentation - */ -fun function(/** parameter */ x: Int) { -} \ No newline at end of file diff --git a/test/data/functions/functionWithReceiver.kt b/test/data/functions/functionWithReceiver.kt deleted file mode 100644 index c8473251..00000000 --- a/test/data/functions/functionWithReceiver.kt +++ /dev/null @@ -1,11 +0,0 @@ -/** - * Function with receiver - */ -fun String.fn() { -} - -/** - * Function with receiver - */ -fun String.fn(x: Int) { -} diff --git a/test/data/functions/genericFunction.kt b/test/data/functions/genericFunction.kt deleted file mode 100644 index 05a65070..00000000 --- a/test/data/functions/genericFunction.kt +++ /dev/null @@ -1,5 +0,0 @@ - -/** - * generic function - */ -private fun generic() {} \ No newline at end of file diff --git a/test/data/functions/genericFunctionWithConstraints.kt b/test/data/functions/genericFunctionWithConstraints.kt deleted file mode 100644 index 5f22f8c5..00000000 --- a/test/data/functions/genericFunctionWithConstraints.kt +++ /dev/null @@ -1,6 +0,0 @@ - -/** - * generic function - */ -public fun generic() { -} \ No newline at end of file diff --git a/test/data/functions/inlineFunction.kt b/test/data/functions/inlineFunction.kt deleted file mode 100644 index 11c19672..00000000 --- a/test/data/functions/inlineFunction.kt +++ /dev/null @@ -1,2 +0,0 @@ -inline fun f() { -} diff --git a/test/data/java/annotatedAnnotation.java b/test/data/java/annotatedAnnotation.java deleted file mode 100644 index 6296e400..00000000 --- a/test/data/java/annotatedAnnotation.java +++ /dev/null @@ -1,6 +0,0 @@ -import java.lang.annotation.*; - -@Target({ElementType.FIELD, ElementType.TYPE, ElementType.METHOD}) -public @interface Attribute { - String value() default ""; -} diff --git a/test/data/java/arrayType.java b/test/data/java/arrayType.java deleted file mode 100644 index dc42a207..00000000 --- a/test/data/java/arrayType.java +++ /dev/null @@ -1,5 +0,0 @@ -class Test { - public String[] arrayToString(int[] data) { - return null; - } -} diff --git a/test/data/java/constructors.java b/test/data/java/constructors.java deleted file mode 100644 index 6f899d18..00000000 --- a/test/data/java/constructors.java +++ /dev/null @@ -1,5 +0,0 @@ -class Test { - public Test() {} - - public Test(String s) {} -} diff --git a/test/data/java/deprecation.java b/test/data/java/deprecation.java deleted file mode 100644 index be8decd6..00000000 --- a/test/data/java/deprecation.java +++ /dev/null @@ -1,6 +0,0 @@ -class C { - /** - * @deprecated This should no longer be used - */ - void fn() {} -} \ No newline at end of file diff --git a/test/data/java/enumValues.java b/test/data/java/enumValues.java deleted file mode 100644 index d8dda934..00000000 --- a/test/data/java/enumValues.java +++ /dev/null @@ -1,3 +0,0 @@ -enum E { - Foo -} \ No newline at end of file diff --git a/test/data/java/field.java b/test/data/java/field.java deleted file mode 100644 index d9ae75f9..00000000 --- a/test/data/java/field.java +++ /dev/null @@ -1,4 +0,0 @@ -class Test { - public int i; - public static final String s; -} diff --git a/test/data/java/inheritorLinks.java b/test/data/java/inheritorLinks.java deleted file mode 100644 index 2378f5c6..00000000 --- a/test/data/java/inheritorLinks.java +++ /dev/null @@ -1,7 +0,0 @@ -class C { - public static class Foo { - } - - public static class Bar extends Foo { - } -} diff --git a/test/data/java/innerClass.java b/test/data/java/innerClass.java deleted file mode 100644 index 0f1be948..00000000 --- a/test/data/java/innerClass.java +++ /dev/null @@ -1,4 +0,0 @@ -class Test { - public class D { - } -} diff --git a/test/data/java/javaLangObject.java b/test/data/java/javaLangObject.java deleted file mode 100644 index be3dd570..00000000 --- a/test/data/java/javaLangObject.java +++ /dev/null @@ -1,3 +0,0 @@ -class Test { - public Object fn() { return null; } -} diff --git a/test/data/java/member.java b/test/data/java/member.java deleted file mode 100644 index d4f4b8d5..00000000 --- a/test/data/java/member.java +++ /dev/null @@ -1,11 +0,0 @@ -class Test { - /** - * Summary for Function - * @param name is String parameter - * @param value is int parameter - * @author yole - */ - public void fn(String name, int value) { - - } -} \ No newline at end of file diff --git a/test/data/java/memberWithModifiers.java b/test/data/java/memberWithModifiers.java deleted file mode 100644 index ea645c21..00000000 --- a/test/data/java/memberWithModifiers.java +++ /dev/null @@ -1,12 +0,0 @@ -public abstract class Test { - /** - * Summary for Function - * @param name is String parameter - * @param value is int parameter - */ - protected final void fn(String name, int value) { - - } - - protected void openFn() {} -} \ No newline at end of file diff --git a/test/data/java/staticMethod.java b/test/data/java/staticMethod.java deleted file mode 100644 index a2ecd7f1..00000000 --- a/test/data/java/staticMethod.java +++ /dev/null @@ -1,4 +0,0 @@ -class C { - public static void foo() { - } -} diff --git a/test/data/java/superClass.java b/test/data/java/superClass.java deleted file mode 100644 index 31b5fa96..00000000 --- a/test/data/java/superClass.java +++ /dev/null @@ -1,2 +0,0 @@ -public class Foo extends Exception implements Cloneable { -} diff --git a/test/data/java/typeParameter.java b/test/data/java/typeParameter.java deleted file mode 100644 index 5a24b30a..00000000 --- a/test/data/java/typeParameter.java +++ /dev/null @@ -1,3 +0,0 @@ -class Foo> { - public E foo(); -} diff --git a/test/data/java/varargs.java b/test/data/java/varargs.java deleted file mode 100644 index d184564e..00000000 --- a/test/data/java/varargs.java +++ /dev/null @@ -1,3 +0,0 @@ -class Foo { - public void bar(String... x); -} diff --git a/test/data/links/linkToJDK.kt b/test/data/links/linkToJDK.kt deleted file mode 100644 index e69de29b..00000000 diff --git a/test/data/links/linkToMember.kt b/test/data/links/linkToMember.kt deleted file mode 100644 index b60eaedb..00000000 --- a/test/data/links/linkToMember.kt +++ /dev/null @@ -1,6 +0,0 @@ -/** - * This is link to [member] - */ -class Foo { - fun member() {} -} \ No newline at end of file diff --git a/test/data/links/linkToParam.kt b/test/data/links/linkToParam.kt deleted file mode 100644 index ca42a742..00000000 --- a/test/data/links/linkToParam.kt +++ /dev/null @@ -1,5 +0,0 @@ -/** - * This is link to [param] - */ -fun Foo(param: String) { -} \ No newline at end of file diff --git a/test/data/links/linkToQualifiedMember.kt b/test/data/links/linkToQualifiedMember.kt deleted file mode 100644 index 22c154fe..00000000 --- a/test/data/links/linkToQualifiedMember.kt +++ /dev/null @@ -1,6 +0,0 @@ -/** - * This is link to [Foo.member] - */ -class Foo { - fun member() {} -} \ No newline at end of file diff --git a/test/data/links/linkToSelf.kt b/test/data/links/linkToSelf.kt deleted file mode 100644 index 74395f0f..00000000 --- a/test/data/links/linkToSelf.kt +++ /dev/null @@ -1,6 +0,0 @@ -/** - * This is link to [Foo] - */ -class Foo { - -} \ No newline at end of file diff --git a/test/data/markdown/spec.txt b/test/data/markdown/spec.txt deleted file mode 100644 index fce87924..00000000 --- a/test/data/markdown/spec.txt +++ /dev/null @@ -1,6150 +0,0 @@ ---- -title: CommonMark Spec -author: -- John MacFarlane -version: 2 -date: 2014-09-19 -... - -# Introduction - -## What is Markdown? - -Markdown is a plain text format for writing structured documents, -based on conventions used for indicating formatting in email and -usenet posts. It was developed in 2004 by John Gruber, who wrote -the first Markdown-to-HTML converter in perl, and it soon became -widely used in websites. By 2014 there were dozens of -implementations in many languages. Some of them extended basic -Markdown syntax with conventions for footnotes, definition lists, -tables, and other constructs, and some allowed output not just in -HTML but in LaTeX and many other formats. - -## Why is a spec needed? - -John Gruber's [canonical description of Markdown's -syntax](http://daringfireball.net/projects/markdown/syntax) -does not specify the syntax unambiguously. Here are some examples of -questions it does not answer: - -1. How much indentation is needed for a sublist? The spec says that - continuation paragraphs need to be indented four spaces, but is - not fully explicit about sublists. It is natural to think that - they, too, must be indented four spaces, but `Markdown.pl` does - not require that. This is hardly a "corner case," and divergences - between implementations on this issue often lead to surprises for - users in real documents. (See [this comment by John - Gruber](http://article.gmane.org/gmane.text.markdown.general/1997).) - -2. Is a blank line needed before a block quote or header? - Most implementations do not require the blank line. However, - this can lead to unexpected results in hard-wrapped text, and - also to ambiguities in parsing (note that some implementations - put the header inside the blockquote, while others do not). - (John Gruber has also spoken [in favor of requiring the blank - lines](http://article.gmane.org/gmane.text.markdown.general/2146).) - -3. Is a blank line needed before an indented code block? - (`Markdown.pl` requires it, but this is not mentioned in the - documentation, and some implementations do not require it.) - - ``` markdown - paragraph - code? - ``` - -4. What is the exact rule for determining when list items get - wrapped in `

` tags? Can a list be partially "loose" and partially - "tight"? What should we do with a list like this? - - ``` markdown - 1. one - - 2. two - 3. three - ``` - - Or this? - - ``` markdown - 1. one - - a - - - b - 2. two - ``` - - (There are some relevant comments by John Gruber - [here](http://article.gmane.org/gmane.text.markdown.general/2554).) - -5. Can list markers be indented? Can ordered list markers be right-aligned? - - ``` markdown - 8. item 1 - 9. item 2 - 10. item 2a - ``` - -6. Is this one list with a horizontal rule in its second item, - or two lists separated by a horizontal rule? - - ``` markdown - * a - * * * * * - * b - ``` - -7. When list markers change from numbers to bullets, do we have - two lists or one? (The Markdown syntax description suggests two, - but the perl scripts and many other implementations produce one.) - - ``` markdown - 1. fee - 2. fie - - foe - - fum - ``` - -8. What are the precedence rules for the markers of inline structure? - For example, is the following a valid link, or does the code span - take precedence ? - - ``` markdown - [a backtick (`)](/url) and [another backtick (`)](/url). - ``` - -9. What are the precedence rules for markers of emphasis and strong - emphasis? For example, how should the following be parsed? - - ``` markdown - *foo *bar* baz* - ``` - -10. What are the precedence rules between block-level and inline-level - structure? For example, how should the following be parsed? - - ``` markdown - - `a long code span can contain a hyphen like this - - and it can screw things up` - ``` - -11. Can list items include headers? (`Markdown.pl` does not allow this, - but headers can occur in blockquotes.) - - ``` markdown - - # Heading - ``` - -12. Can link references be defined inside block quotes or list items? - - ``` markdown - > Blockquote [foo]. - > - > [foo]: /url - ``` - -13. If there are multiple definitions for the same reference, which takes - precedence? - - ``` markdown - [foo]: /url1 - [foo]: /url2 - - [foo][] - ``` - -In the absence of a spec, early implementers consulted `Markdown.pl` -to resolve these ambiguities. But `Markdown.pl` was quite buggy, and -gave manifestly bad results in many cases, so it was not a -satisfactory replacement for a spec. - -Because there is no unambiguous spec, implementations have diverged -considerably. As a result, users are often surprised to find that -a document that renders one way on one system (say, a github wiki) -renders differently on another (say, converting to docbook using -pandoc). To make matters worse, because nothing in Markdown counts -as a "syntax error," the divergence often isn't discovered right away. - -## About this document - -This document attempts to specify Markdown syntax unambiguously. -It contains many examples with side-by-side Markdown and -HTML. These are intended to double as conformance tests. An -accompanying script `runtests.pl` can be used to run the tests -against any Markdown program: - - perl runtests.pl spec.txt PROGRAM - -Since this document describes how Markdown is to be parsed into -an abstract syntax tree, it would have made sense to use an abstract -representation of the syntax tree instead of HTML. But HTML is capable -of representing the structural distinctions we need to make, and the -choice of HTML for the tests makes it possible to run the tests against -an implementation without writing an abstract syntax tree renderer. - -This document is generated from a text file, `spec.txt`, written -in Markdown with a small extension for the side-by-side tests. -The script `spec2md.pl` can be used to turn `spec.txt` into pandoc -Markdown, which can then be converted into other formats. - -In the examples, the `→` character is used to represent tabs. - -# Preprocessing - -A [line](#line) -is a sequence of zero or more characters followed by a line -ending (CR, LF, or CRLF) or by the end of -file. - -This spec does not specify an encoding; it thinks of lines as composed -of characters rather than bytes. A conforming parser may be limited -to a certain encoding. - -Tabs in lines are expanded to spaces, with a tab stop of 4 characters: - -. -→foo→baz→→bim -. -

foo baz     bim
-
-. - -. - a→a - ὐ→a -. -
a   a
-ὐ   a
-
-. - -Line endings are replaced by newline characters (LF). - -A line containing no characters, or a line containing only spaces (after -tab expansion), is called a [blank line](#blank-line). - - -# Blocks and inlines - -We can think of a document as a sequence of [blocks](#block)---structural elements like paragraphs, block quotations, -lists, headers, rules, and code blocks. Blocks can contain other -blocks, or they can contain [inline](#inline) content: -words, spaces, links, emphasized text, images, and inline code. - -## Precedence - -Indicators of block structure always take precedence over indicators -of inline structure. So, for example, the following is a list with -two items, not a list with one item containing a code span: - -. -- `one -- two` -. -
    -
  • `one
    • -
  • two`
    • -
-. - -This means that parsing can proceed in two steps: first, the block -structure of the document can be discerned; second, text lines inside -paragraphs, headers, and other block constructs can be parsed for inline -structure. The second step requires information about link reference -definitions that will be available only at the end of the first -step. Note that the first step requires processing lines in sequence, -but the second can be parallelized, since the inline parsing of -one block element does not affect the inline parsing of any other. - -## Container blocks and leaf blocks - -We can divide blocks into two types: -[container blocks](#container-block), -which can contain other blocks, and [leaf blocks](#leaf-block), - which cannot. - -# Leaf blocks - -This section describes the different kinds of leaf block that make up a -Markdown document. - -## Horizontal rules - -A line consisting of 0-3 spaces of indentation, followed by a sequence -of three or more matching `-`, `_`, or `*` characters, each followed -optionally by any number of spaces, forms a [horizontal -rule](#horizontal-rule). - -. -*** ---- -___ -. -
-
-
-. - -Wrong characters: - -. -+++ -. -

+++

-. - -. -=== -. -

===

-. - -Not enough characters: - -. --- -** -__ -. -

-- -** -__

-. - -One to three spaces indent are allowed: - -. - *** - *** - *** -. -
-
-
-. - -Four spaces is too many: - -. - *** -. -
***
-
-. - -. -Foo - *** -. -

Foo -***

-. - -More than three characters may be used: - -. -_____________________________________ -. -
-. - -Spaces are allowed between the characters: - -. - - - - -. -
-. - -. - ** * ** * ** * ** -. -
-. - -. -- - - - -. -
-. - -Spaces are allowed at the end: - -. -- - - - -. -
-. - -However, no other characters may occur at the end or the -beginning: - -. -_ _ _ _ a - -a------ -. -

_ _ _ _ a

-

a------

-. - -It is required that all of the non-space characters be the same. -So, this is not a horizontal rule: - -. - *-* -. -

-

-. - -Horizontal rules do not need blank lines before or after: - -. -- foo -*** -- bar -. -
    -
  • foo
    • -
-
-
    -
  • bar
    • -
-. - -Horizontal rules can interrupt a paragraph: - -. -Foo -*** -bar -. -

Foo

-
-

bar

-. - -Note, however, that this is a setext header, not a paragraph followed -by a horizontal rule: - -. -Foo ---- -bar -. -

Foo

-

bar

-. - -When both a horizontal rule and a list item are possible -interpretations of a line, the horizontal rule is preferred: - -. -* Foo -* * * -* Bar -. -
    -
  • Foo
    • -
-
-
    -
  • Bar
    • -
-. - -If you want a horizontal rule in a list item, use a different bullet: - -. -- Foo -- * * * -. -
    -
  • Foo
    • -
    • -
-. - -## ATX headers - -An [ATX header](#atx-header) -consists of a string of characters, parsed as inline content, between an -opening sequence of 1--6 unescaped `#` characters and an optional -closing sequence of any number of `#` characters. The opening sequence -of `#` characters cannot be followed directly by a nonspace character. -The closing `#` characters may be followed by spaces only. The opening -`#` character may be indented 0-3 spaces. The raw contents of the -header are stripped of leading and trailing spaces before being parsed -as inline content. The header level is equal to the number of `#` -characters in the opening sequence. - -Simple headers: - -. -# foo -## foo -### foo -#### foo -##### foo -###### foo -. -

foo

-

foo

-

foo

-

foo

-
foo
-
foo
-. - -More than six `#` characters is not a header: - -. -####### foo -. -

####### foo

-. - -A space is required between the `#` characters and the header's -contents. Note that many implementations currently do not require -the space. However, the space was required by the [original ATX -implementation](http://www.aaronsw.com/2002/atx/atx.py), and it helps -prevent things like the following from being parsed as headers: - -. -#5 bolt -. -

#5 bolt

-. - -This is not a header, because the first `#` is escaped: - -. -\## foo -. -

## foo

-. - -Contents are parsed as inlines: - -. -# foo *bar* \*baz\* -. -

foo bar *baz*

-. - -Leading and trailing blanks are ignored in parsing inline content: - -. -# foo -. -

foo

-. - -One to three spaces indentation are allowed: - -. - ### foo - ## foo - # foo -. -

foo

-

foo

-

foo

-. - -Four spaces are too much: - -. - # foo -. -
# foo
-
-. - -. -foo - # bar -. -

foo -# bar

-. - -A closing sequence of `#` characters is optional: - -. -## foo ## - ### bar ### -. -

foo

-

bar

-. - -It need not be the same length as the opening sequence: - -. -# foo ################################## -##### foo ## -. -

foo

-
foo
-. - -Spaces are allowed after the closing sequence: - -. -### foo ### -. -

foo

-. - -A sequence of `#` characters with a nonspace character following it -is not a closing sequence, but counts as part of the contents of the -header: - -. -### foo ### b -. -

foo ### b

-. - -Backslash-escaped `#` characters do not count as part -of the closing sequence: - -. -### foo \### -## foo \#\## -# foo \# -. -

foo #

-

foo ##

-

foo #

-. - -ATX headers need not be separated from surrounding content by blank -lines, and they can interrupt paragraphs: - -. -**** -## foo -**** -. -
-

foo

-
-. - -. -Foo bar -# baz -Bar foo -. -

Foo bar

-

baz

-

Bar foo

-. - -ATX headers can be empty: - -. -## -# -### ### -. -

-

-

-. - -## Setext headers - -A [setext header](#setext-header) -consists of a line of text, containing at least one nonspace character, -with no more than 3 spaces indentation, followed by a [setext header -underline](#setext-header-underline). A [setext header -underline](#setext-header-underline) -is a sequence of `=` characters or a sequence of `-` characters, with no -more than 3 spaces indentation and any number of trailing -spaces. The header is a level 1 header if `=` characters are used, and -a level 2 header if `-` characters are used. The contents of the header -are the result of parsing the first line as Markdown inline content. - -In general, a setext header need not be preceded or followed by a -blank line. However, it cannot interrupt a paragraph, so when a -setext header comes after a paragraph, a blank line is needed between -them. - -Simple examples: - -. -Foo *bar* -========= - -Foo *bar* ---------- -. -

Foo bar

-

Foo bar

-. - -The underlining can be any length: - -. -Foo -------------------------- - -Foo -= -. -

Foo

-

Foo

-. - -The header content can be indented up to three spaces, and need -not line up with the underlining: - -. - Foo ---- - - Foo ------ - - Foo - === -. -

Foo

-

Foo

-

Foo

-. - -Four spaces indent is too much: - -. - Foo - --- - - Foo ---- -. -
Foo
----
-
-Foo
-
-
-. - -The setext header underline can be indented up to three spaces, and -may have trailing spaces: - -. -Foo - ---- -. -

Foo

-. - -Four spaces is too much: - -. -Foo - --- -. -

Foo ----

-. - -The setext header underline cannot contain internal spaces: - -. -Foo -= = - -Foo ---- - -. -

Foo -= =

-

Foo

-
-. - -Trailing spaces in the content line do not cause a line break: - -. -Foo ------ -. -

Foo

-. - -Nor does a backslash at the end: - -. -Foo\ ----- -. -

Foo\

-. - -Since indicators of block structure take precedence over -indicators of inline structure, the following are setext headers: - -. -`Foo ----- -` - - -. -

`Foo

-

`

-

<a title="a lot

-

of dashes"/>

-. - -The setext header underline cannot be a lazy line: - -. -> Foo ---- -. -
-

Foo

-
-
-. - -A setext header cannot interrupt a paragraph: - -. -Foo -Bar ---- - -Foo -Bar -=== -. -

Foo -Bar

-
-

Foo -Bar -===

-. - -But in general a blank line is not required before or after: - -. ---- -Foo ---- -Bar ---- -Baz -. -
-

Foo

-

Bar

-

Baz

-. - -Setext headers cannot be empty: - -. - -==== -. -

====

-. - - -## Indented code blocks - -An [indented code block](#indented-code-block) - is composed of one or more -[indented chunks](#indented-chunk) separated by blank lines. -An [indented chunk](#indented-chunk) -is a sequence of non-blank lines, each indented four or more -spaces. An indented code block cannot interrupt a paragraph, so -if it occurs before or after a paragraph, there must be an -intervening blank line. The contents of the code block are -the literal contents of the lines, including trailing newlines, -minus four spaces of indentation. An indented code block has no -attributes. - -. - a simple - indented code block -. -
a simple
-  indented code block
-
-. - -The contents are literal text, and do not get parsed as Markdown: - -. - - *hi* - - - one -. -
<a/>
-*hi*
-
-- one
-
-. - -Here we have three chunks separated by blank lines: - -. - chunk1 - - chunk2 - - - - chunk3 -. -
chunk1
-
-chunk2
-
-
-
-chunk3
-
-. - -Any initial spaces beyond four will be included in the content, even -in interior blank lines: - -. - chunk1 - - chunk2 -. -
chunk1
-  
-  chunk2
-
-. - -An indented code block cannot interrupt a paragraph. (This -allows hanging indents and the like.) - -. -Foo - bar - -. -

Foo -bar

-. - -However, any non-blank line with fewer than four leading spaces ends -the code block immediately. So a paragraph may occur immediately -after indented code: - -. - foo -bar -. -
foo
-
-

bar

-. - -And indented code can occur immediately before and after other kinds of -blocks: - -. -# Header - foo -Header ------- - foo ----- -. -

Header

-
foo
-
-

Header

-
foo
-
-
-. - -The first line can be indented more than four spaces: - -. - foo - bar -. -
    foo
-bar
-
-. - -Blank lines preceding or following an indented code block -are not included in it: - -. - - - foo - - -. -
foo
-
-. - -Trailing spaces are included in the code block's content: - -. - foo -. -
foo  
-
-. - - -## Fenced code blocks - -A [code fence](#code-fence) is a sequence -of at least three consecutive backtick characters (`` ` ``) or -tildes (`~`). (Tildes and backticks cannot be mixed.) -A [fenced code block](#fenced-code-block) -begins with a code fence, indented no more than three spaces. - -The line with the opening code fence may optionally contain some text -following the code fence; this is trimmed of leading and trailing -spaces and called the [info string](#info-string). - The info string may not contain any backtick -characters. (The reason for this restriction is that otherwise -some inline code would be incorrectly interpreted as the -beginning of a fenced code block.) - -The content of the code block consists of all subsequent lines, until -a closing [code fence](#code-fence) of the same type as the code block -began with (backticks or tildes), and with at least as many backticks -or tildes as the opening code fence. If the leading code fence is -indented N spaces, then up to N spaces of indentation are removed from -each line of the content (if present). (If a content line is not -indented, it is preserved unchanged. If it is indented less than N -spaces, all of the indentation is removed.) - -The closing code fence may be indented up to three spaces, and may be -followed only by spaces, which are ignored. If the end of the -containing block (or document) is reached and no closing code fence -has been found, the code block contains all of the lines after the -opening code fence until the end of the containing block (or -document). (An alternative spec would require backtracking in the -event that a closing code fence is not found. But this makes parsing -much less efficient, and there seems to be no real down side to the -behavior described here.) - -A fenced code block may interrupt a paragraph, and does not require -a blank line either before or after. - -The content of a code fence is treated as literal text, not parsed -as inlines. The first word of the info string is typically used to -specify the language of the code sample, and rendered in the `class` -attribute of the `code` tag. However, this spec does not mandate any -particular treatment of the info string. - -Here is a simple example with backticks: - -. -``` -< - > -``` -. -
<
- >
-
-. - -With tildes: - -. -~~~ -< - > -~~~ -. -
<
- >
-
-. - -The closing code fence must use the same character as the opening -fence: - -. -``` -aaa -~~~ -``` -. -
aaa
-~~~
-
-. - -. -~~~ -aaa -``` -~~~ -. -
aaa
-```
-
-. - -The closing code fence must be at least as long as the opening fence: - -. -```` -aaa -``` -`````` -. -
aaa
-```
-
-. - -. -~~~~ -aaa -~~~ -~~~~ -. -
aaa
-~~~
-
-. - -Unclosed code blocks are closed by the end of the document: - -. -``` -. -
-. - -. -````` - -``` -aaa -. -

-```
-aaa
-
-. - -A code block can have all empty lines as its content: - -. -``` - - -``` -. -

-  
-
-. - -A code block can be empty: - -. -``` -``` -. -
-. - -Fences can be indented. If the opening fence is indented, -content lines will have equivalent opening indentation removed, -if present: - -. - ``` - aaa -aaa -``` -. -
aaa
-aaa
-
-. - -. - ``` -aaa - aaa -aaa - ``` -. -
aaa
-aaa
-aaa
-
-. - -. - ``` - aaa - aaa - aaa - ``` -. -
aaa
- aaa
-aaa
-
-. - -Four spaces indentation produces an indented code block: - -. - ``` - aaa - ``` -. -
```
-aaa
-```
-
-. - -Code fences (opening and closing) cannot contain internal spaces: - -. -``` ``` -aaa -. -

-aaa

-. - -. -~~~~~~ -aaa -~~~ ~~ -. -
aaa
-~~~ ~~
-
-. - -Fenced code blocks can interrupt paragraphs, and can be followed -directly by paragraphs, without a blank line between: - -. -foo -``` -bar -``` -baz -. -

foo

-
bar
-
-

baz

-. - -Other blocks can also occur before and after fenced code blocks -without an intervening blank line: - -. -foo ---- -~~~ -bar -~~~ -# baz -. -

foo

-
bar
-
-

baz

-. - -An [info string](#info-string) can be provided after the opening code fence. -Opening and closing spaces will be stripped, and the first word, prefixed -with `language-`, is used as the value for the `class` attribute of the -`code` element within the enclosing `pre` element. - -. -```ruby -def foo(x) - return 3 -end -``` -. -
def foo(x)
-  return 3
-end
-
-. - -. -~~~~ ruby startline=3 $%@#$ -def foo(x) - return 3 -end -~~~~~~~ -. -
def foo(x)
-  return 3
-end
-
-. - -. -````; -```` -. -
-. - -Info strings for backtick code blocks cannot contain backticks: - -. -``` aa ``` -foo -. -

aa -foo

-. - -Closing code fences cannot have info strings: - -. -``` -``` aaa -``` -. -
``` aaa
-
-. - - -## HTML blocks - -An [HTML block tag](#html-block-tag) is -an [open tag](#open-tag) or [closing tag](#closing-tag) whose tag -name is one of the following (case-insensitive): -`article`, `header`, `aside`, `hgroup`, `blockquote`, `hr`, `iframe`, -`body`, `li`, `map`, `button`, `object`, `canvas`, `ol`, `caption`, -`output`, `col`, `p`, `colgroup`, `pre`, `dd`, `progress`, `div`, -`section`, `dl`, `table`, `td`, `dt`, `tbody`, `embed`, `textarea`, -`fieldset`, `tfoot`, `figcaption`, `th`, `figure`, `thead`, `footer`, -`footer`, `tr`, `form`, `ul`, `h1`, `h2`, `h3`, `h4`, `h5`, `h6`, -`video`, `script`, `style`. - -An [HTML block](#html-block) begins with an -[HTML block tag](#html-block-tag), [HTML comment](#html-comment), -[processing instruction](#processing-instruction), -[declaration](#declaration), or [CDATA section](#cdata-section). -It ends when a [blank line](#blank-line) or the end of the -input is encountered. The initial line may be indented up to three -spaces, and subsequent lines may have any indentation. The contents -of the HTML block are interpreted as raw HTML, and will not be escaped -in HTML output. - -Some simple examples: - -. - - - - -
- hi -
- -okay. -. - - - - -
- hi -
-

okay.

-. - -. -
- *hello* - -. -
- *hello* - -. - -Here we have two code blocks with a Markdown paragraph between them: - -. -
- -*Markdown* - -
-. -
-

Markdown

-
-. - -In the following example, what looks like a Markdown code block -is actually part of the HTML block, which continues until a blank -line or the end of the document is reached: - -. -
-``` c -int x = 33; -``` -. -
-``` c -int x = 33; -``` -. - -A comment: - -. - -. - -. - -A processing instruction: - -. - -. - -. - -CDATA: - -. - -. - -. - -The opening tag can be indented 1-3 spaces, but not 4: - -. - - - -. - -
<!-- foo -->
-
-. - -An HTML block can interrupt a paragraph, and need not be preceded -by a blank line. - -. -Foo -
-bar -
-. -

Foo

-
-bar -
-. - -However, a following blank line is always needed, except at the end of -a document: - -. -
-bar -
-*foo* -. -
-bar -
-*foo* -. - -An incomplete HTML block tag may also start an HTML block: - -. -
The only restrictions are that block-level HTML elements — -> e.g. `
`, ``, `
`, `
`, etc. — must be separated from
-> surrounding content by blank lines, and the start and end tags of the
-> block should not be indented with tabs or spaces.
-
-In some ways Gruber's rule is more restrictive than the one given
-here:
-
-- It requires that an HTML block be preceded by a blank line.
-- It does not allow the start tag to be indented.
-- It requires a matching end tag, which it also does not allow to
-  be indented.
-
-Indeed, most Markdown implementations, including some of Gruber's
-own perl implementations, do not impose these restrictions.
-
-There is one respect, however, in which Gruber's rule is more liberal
-than the one given here, since it allows blank lines to occur inside
-an HTML block.  There are two reasons for disallowing them here.
-First, it removes the need to parse balanced tags, which is
-expensive and can require backtracking from the end of the document
-if no matching end tag is found. Second, it provides a very simple
-and flexible way of including Markdown content inside HTML tags:
-simply separate the Markdown from the HTML using blank lines:
-
-.
-

-
-*Emphasized* text.
-
-

-.
-

-
Emphasized text.

-

-.
-
-Compare:
-
-.
-

-*Emphasized* text.
-

-.
-

-*Emphasized* text.
-

-.
-
-Some Markdown implementations have adopted a convention of
-interpreting content inside tags as text if the open tag has
-the attribute `markdown=1`.  The rule given above seems a simpler and
-more elegant way of achieving the same expressive power, which is also
-much simpler to parse.
-
-The main potential drawback is that one can no longer paste HTML
-blocks into Markdown documents with 100% reliability.  However,
-*in most cases* this will work fine, because the blank lines in
-HTML are usually followed by HTML block tags.  For example:
-
-.
-
- - - - - - - -
-Hi -
-. - - - - -
-Hi -
-. - -Moreover, blank lines are usually not necessary and can be -deleted. The exception is inside `
` tags; here, one can
-replace the blank lines with `
` entities.
-
-So there is no important loss of expressive power with the new rule.
-
-## Link reference definitions
-
-A [link reference definition](#link-reference-definition)
- consists of a [link
-label](#link-label), indented up to three spaces, followed
-by a colon (`:`), optional blank space (including up to one
-newline), a [link destination](#link-destination), optional
-blank space (including up to one newline), and an optional [link
-title](#link-title), which if it is present must be separated
-from the [link destination](#link-destination) by whitespace.
-No further non-space characters may occur on the line.
-
-A [link reference-definition](#link-reference-definition)
-does not correspond to a structural element of a document.  Instead, it
-defines a label which can be used in [reference links](#reference-link)
-and reference-style [images](#image) elsewhere in the document.  [Link
-reference definitions] can come either before or after the links that use
-them.
-
-.
-[foo]: /url "title"
-
-[foo]
-.
-
foo

-.
-
-.
-   [foo]: 
-      /url  
-           'the title'  
-
-[foo]
-.
-
foo

-.
-
-.
-[Foo*bar\]]:my_(url) 'title (with parens)'
-
-[Foo*bar\]]
-.
-
Foo*bar]

-.
-
-.
-[Foo bar]:
-
-'title'
-
-[Foo bar]
-.
-
Foo bar

-.
-
-The title may be omitted:
-
-.
-[foo]:
-/url
-
-[foo]
-.
-
foo

-.
-
-The link destination may not be omitted:
-
-.
-[foo]:
-
-[foo]
-.
-
[foo]:

-
[foo]

-.
-
-A link can come before its corresponding definition:
-
-.
-[foo]
-
-[foo]: url
-.
-
foo

-.
-
-If there are several matching definitions, the first one takes
-precedence:
-
-.
-[foo]
-
-[foo]: first
-[foo]: second
-.
-
foo

-.
-
-As noted in the section on [Links], matching of labels is
-case-insensitive (see [matches](#matches)).
-
-.
-[FOO]: /url
-
-[Foo]
-.
-
Foo

-.
-
-.
-[ΑΓΩ]: /φου
-
-[αγω]
-.
-
αγω

-.
-
-Here is a link reference definition with no corresponding link.
-It contributes nothing to the document.
-
-.
-[foo]: /url
-.
-.
-
-This is not a link reference definition, because there are
-non-space characters after the title:
-
-.
-[foo]: /url "title" ok
-.
-
[foo]: /url "title" ok

-.
-
-This is not a link reference definition, because it is indented
-four spaces:
-
-.
-    [foo]: /url "title"
-
-[foo]
-.
-
[foo]: /url "title"
-

-
[foo]

-.
-
-This is not a link reference definition, because it occurs inside
-a code block:
-
-.
-```
-[foo]: /url
-```
-
-[foo]
-.
-
[foo]: /url
-

-
[foo]

-.
-
-A [link reference definition](#link-reference-definition) cannot
-interrupt a paragraph.
-
-.
-Foo
-[bar]: /baz
-
-[bar]
-.
-
Foo
-[bar]: /baz

-
[bar]

-.
-
-However, it can directly follow other block elements, such as headers
-and horizontal rules, and it need not be followed by a blank line.
-
-.
-# [Foo]
-[foo]: /url
-> bar
-.
-
Foo

-

-
bar

-

-.
-
-Several [link references](#link-reference) can occur one after another,
-without intervening blank lines.
-
-.
-[foo]: /foo-url "foo"
-[bar]: /bar-url
-  "bar"
-[baz]: /baz-url
-
-[foo],
-[bar],
-[baz]
-.
-
foo,
-bar,
-baz

-.
-
-[Link reference definitions](#link-reference-definition) can occur
-inside block containers, like lists and block quotations.  They
-affect the entire document, not just the container in which they
-are defined:
-
-.
-[foo]
-
-> [foo]: /url
-.
-
foo

-

-

-.
-
-
-## Paragraphs
-
-A sequence of non-blank lines that cannot be interpreted as other
-kinds of blocks forms a [paragraph](#paragraph).
-The contents of the paragraph are the result of parsing the
-paragraph's raw content as inlines.  The paragraph's raw content
-is formed by concatenating the lines and removing initial and final
-spaces.
-
-A simple example with two paragraphs:
-
-.
-aaa
-
-bbb
-.
-
aaa

-
bbb

-.
-
-Paragraphs can contain multiple lines, but no blank lines:
-
-.
-aaa
-bbb
-
-ccc
-ddd
-.
-
aaa
-bbb

-
ccc
-ddd

-.
-
-Multiple blank lines between paragraph have no effect:
-
-.
-aaa
-
-
-bbb
-.
-
aaa

-
bbb

-.
-
-Leading spaces are skipped:
-
-.
-  aaa
- bbb
-.
-
aaa
-bbb

-.
-
-Lines after the first may be indented any amount, since indented
-code blocks cannot interrupt paragraphs.
-
-.
-aaa
-             bbb
-                                       ccc
-.
-
aaa
-bbb
-ccc

-.
-
-However, the first line may be indented at most three spaces,
-or an indented code block will be triggered:
-
-.
-   aaa
-bbb
-.
-
aaa
-bbb

-.
-
-.
-    aaa
-bbb
-.
-
aaa
-

-
bbb

-.
-
-Final spaces are stripped before inline parsing, so a paragraph
-that ends with two or more spaces will not end with a hard line
-break:
-
-.
-aaa     
-bbb     
-.
-
aaa

-bbb

-.
-
-## Blank lines
-
-[Blank lines](#blank-line) between block-level elements are ignored,
-except for the role they play in determining whether a [list](#list)
-is [tight](#tight) or [loose](#loose).
-
-Blank lines at the beginning and end of the document are also ignored.
-
-.
-  
-
-aaa
-  
-
-# aaa
-
-  
-.
-
aaa

-
aaa

-.
-
-
-# Container blocks
-
-A [container block](#container-block) is a block that has other
-blocks as its contents.  There are two basic kinds of container blocks:
-[block quotes](#block-quote) and [list items](#list-item).
-[Lists](#list) are meta-containers for [list items](#list-item).
-
-We define the syntax for container blocks recursively.  The general
-form of the definition is:
-
-> If X is a sequence of blocks, then the result of
-> transforming X in such-and-such a way is a container of type Y
-> with these blocks as its content.
-
-So, we explain what counts as a block quote or list item by explaining
-how these can be *generated* from their contents. This should suffice
-to define the syntax, although it does not give a recipe for *parsing*
-these constructions.  (A recipe is provided below in the section entitled
-[A parsing strategy](#appendix-a-a-parsing-strategy).)
-
-## Block quotes
-
-A [block quote marker](#block-quote-marker) 
-consists of 0-3 spaces of initial indent, plus (a) the character `>` together
-with a following space, or (b) a single character `>` not followed by a space.
-
-The following rules define [block quotes](#block-quote):
-
-
-1.  **Basic case.**  If a string of lines *Ls* constitute a sequence
-    of blocks *Bs*, then the result of appending a [block quote
-    marker](#block-quote-marker) to the beginning of each line in *Ls*
-    is a [block quote](#block-quote) containing *Bs*.
-
-2.  **Laziness.**  If a string of lines *Ls* constitute a [block
-    quote](#block-quote) with contents *Bs*, then the result of deleting
-    the initial [block quote marker](#block-quote-marker) from one or
-    more lines in which the next non-space character after the [block
-    quote marker](#block-quote-marker) is [paragraph continuation
-    text](#paragraph-continuation-text) is a block quote with *Bs* as
-    its content.  
-    [Paragraph continuation text](#paragraph-continuation-text) is text
-    that will be parsed as part of the content of a paragraph, but does
-    not occur at the beginning of the paragraph.
-
-3.  **Consecutiveness.**  A document cannot contain two [block
-    quotes](#block-quote) in a row unless there is a [blank
-    line](#blank-line) between them.
-
-Nothing else counts as a [block quote](#block-quote).
-
-Here is a simple example:
-
-.
-> # Foo
-> bar
-> baz
-.
-

-
Foo

-
bar
-baz

-

-.
-
-The spaces after the `>` characters can be omitted:
-
-.
-># Foo
->bar
-> baz
-.
-

-
Foo

-
bar
-baz

-

-.
-
-The `>` characters can be indented 1-3 spaces:
-
-.
-   > # Foo
-   > bar
- > baz
-.
-

-
Foo

-
bar
-baz

-

-.
-
-Four spaces gives us a code block:
-
-.
-    > # Foo
-    > bar
-    > baz
-.
-
> # Foo
-> bar
-> baz
-

-.
-
-The Laziness clause allows us to omit the `>` before a
-paragraph continuation line:
-
-.
-> # Foo
-> bar
-baz
-.
-

-
Foo

-
bar
-baz

-

-.
-
-A block quote can contain some lazy and some non-lazy
-continuation lines:
-
-.
-> bar
-baz
-> foo
-.
-

-
bar
-baz
-foo

-

-.
-
-Laziness only applies to lines that are continuations of
-paragraphs. Lines containing characters or indentation that indicate
-block structure cannot be lazy.
-
-.
-> foo
----
-.
-

-
foo

-

-

-.
-
-.
-> - foo
-- bar
-.
-

-
    
-
  • foo
    • 
-

-

-
    
-
  • bar
    • 
-

-.
-
-.
->     foo
-    bar
-.
-

-
foo
-

-

-
bar
-

-.
-
-.
-> ```
-foo
-```
-.
-

-

-

-
foo

-

-.
-
-A block quote can be empty:
-
-.
->
-.
-

-

-.
-
-.
->
->  
-> 
-.
-

-

-.
-
-A block quote can have initial or final blank lines:
-
-.
->
-> foo
->  
-.
-

-
foo

-

-.
-
-A blank line always separates block quotes:
-
-.
-> foo
-
-> bar
-.
-

-
foo

-

-

-
bar

-

-.
-
-(Most current Markdown implementations, including John Gruber's
-original `Markdown.pl`, will parse this example as a single block quote
-with two paragraphs.  But it seems better to allow the author to decide
-whether two block quotes or one are wanted.)
-
-Consecutiveness means that if we put these block quotes together,
-we get a single block quote:
-
-.
-> foo
-> bar
-.
-

-
foo
-bar

-

-.
-
-To get a block quote with two paragraphs, use:
-
-.
-> foo
->
-> bar
-.
-

-
foo

-
bar

-

-.
-
-Block quotes can interrupt paragraphs:
-
-.
-foo
-> bar
-.
-
foo

-

-
bar

-

-.
-
-In general, blank lines are not needed before or after block
-quotes:
-
-.
-> aaa
-***
-> bbb
-.
-

-
aaa

-

-

-

-
bbb

-

-.
-
-However, because of laziness, a blank line is needed between
-a block quote and a following paragraph:
-
-.
-> bar
-baz
-.
-

-
bar
-baz

-

-.
-
-.
-> bar
-
-baz
-.
-

-
bar

-

-
baz

-.
-
-.
-> bar
->
-baz
-.
-

-
bar

-

-
baz

-.
-
-It is a consequence of the Laziness rule that any number
-of initial `>`s may be omitted on a continuation line of a
-nested block quote:
-
-.
-> > > foo
-bar
-.
-

-

-

-
foo
-bar

-

-

-

-.
-
-.
->>> foo
-> bar
->>baz
-.
-

-

-

-
foo
-bar
-baz

-

-

-

-.
-
-When including an indented code block in a block quote,
-remember that the [block quote marker](#block-quote-marker) includes
-both the `>` and a following space.  So *five spaces* are needed after
-the `>`:
-
-.
->     code
-
->    not code
-.
-

-
code
-

-

-

-
not code

-

-.
-
-
-## List items
-
-A [list marker](#list-marker)  is a
-[bullet list marker](#bullet-list-marker) or an [ordered list
-marker](#ordered-list-marker).
-
-A [bullet list marker](#bullet-list-marker) 
-is a `-`, `+`, or `*` character.
-
-An [ordered list marker](#ordered-list-marker) 
-is a sequence of one of more digits (`0-9`), followed by either a
-`.` character or a `)` character.
-
-The following rules define [list items](#list-item):
-
-1.  **Basic case.**  If a sequence of lines *Ls* constitute a sequence of
-    blocks *Bs* starting with a non-space character and not separated
-    from each other by more than one blank line, and *M* is a list
-    marker *M* of width *W* followed by 0 < *N* < 5 spaces, then the result
-    of prepending *M* and the following spaces to the first line of
-    *Ls*, and indenting subsequent lines of *Ls* by *W + N* spaces, is a
-    list item with *Bs* as its contents.  The type of the list item
-    (bullet or ordered) is determined by the type of its list marker.
-    If the list item is ordered, then it is also assigned a start
-    number, based on the ordered list marker.
-
-For example, let *Ls* be the lines
-
-.
-A paragraph
-with two lines.
-
-    indented code
-
-> A block quote.
-.
-
A paragraph
-with two lines.

-
indented code
-

-

-
A block quote.

-

-.
-
-And let *M* be the marker `1.`, and *N* = 2.  Then rule #1 says
-that the following is an ordered list item with start number 1,
-and the same contents as *Ls*:
-
-.
-1.  A paragraph
-    with two lines.
-
-        indented code
-
-    > A block quote.
-.
-
    
-
  1. A paragraph
-with two lines.
    
-
    indented code
-
    
-
    
-
    A block quote.
    
-
    2. 
-

-.
-
-The most important thing to notice is that the position of
-the text after the list marker determines how much indentation
-is needed in subsequent blocks in the list item.  If the list
-marker takes up two spaces, and there are three spaces between
-the list marker and the next nonspace character, then blocks
-must be indented five spaces in order to fall under the list
-item.
-
-Here are some examples showing how far content must be indented to be
-put under the list item:
-
-.
-- one
-
- two
-.
-
    
-
  • one
    • 
-

-
two

-.
-
-.
-- one
-
-  two
-.
-
    
-
  • one
    
-
    two
    • 
-

-.
-
-.
- -    one
-
-     two
-.
-
    
-
  • one
    • 
-

-
 two
-

-.
-
-.
- -    one
-
-      two
-.
-
    
-
  • one
    
-
    two
    • 
-

-.
-
-It is tempting to think of this in terms of columns:  the continuation
-blocks must be indented at least to the column of the first nonspace
-character after the list marker.  However, that is not quite right.
-The spaces after the list marker determine how much relative indentation
-is needed.  Which column this indentation reaches will depend on
-how the list item is embedded in other constructions, as shown by
-this example:
-
-.
-   > > 1.  one
->>
->>     two
-.
-

-

-
    
-
  1. one
    
-
    two
    2. 
-

-

-

-.
-
-Here `two` occurs in the same column as the list marker `1.`,
-but is actually contained in the list item, because there is
-sufficent indentation after the last containing blockquote marker.
-
-The converse is also possible.  In the following example, the word `two`
-occurs far to the right of the initial text of the list item, `one`, but
-it is not considered part of the list item, because it is not indented
-far enough past the blockquote marker:
-
-.
->>- one
->>
-  >  > two
-.
-

-

-
    
-
  • one
    • 
-

-
two

-

-

-.
-
-A list item may not contain blocks that are separated by more than
-one blank line.  Thus, two blank lines will end a list, unless the
-two blanks are contained in a [fenced code block](#fenced-code-block).
-
-.
-- foo
-
-  bar
-
-- foo
-
-
-  bar
-
-- ```
-  foo
-
-
-  bar
-  ```
-.
-
    
-
  • foo
    
-
    bar
    • 
-
  • foo
    • 
-

-
bar

-
    
-
  • foo
-
-
-bar
-
    • 
-

-.
-
-A list item may contain any kind of block:
-
-.
-1.  foo
-
-    ```
-    bar
-    ```
-
-    baz
-
-    > bam
-.
-
    
-
  1. foo
    
-
    bar
-
    
-
    baz
    
-
    
-
    bam
    
-
    2. 
-

-.
-
-2.  **Item starting with indented code.**  If a sequence of lines *Ls*
-    constitute a sequence of blocks *Bs* starting with an indented code
-    block and not separated from each other by more than one blank line,
-    and *M* is a list marker *M* of width *W* followed by
-    one space, then the result of prepending *M* and the following
-    space to the first line of *Ls*, and indenting subsequent lines of
-    *Ls* by *W + 1* spaces, is a list item with *Bs* as its contents.
-    If a line is empty, then it need not be indented.  The type of the
-    list item (bullet or ordered) is determined by the type of its list
-    marker.  If the list item is ordered, then it is also assigned a
-    start number, based on the ordered list marker.
-
-An indented code block will have to be indented four spaces beyond
-the edge of the region where text will be included in the list item.
-In the following case that is 6 spaces:
-
-.
-- foo
-
-      bar
-.
-
    
-
  • foo
    
-
    bar
-
    • 
-

-.
-
-And in this case it is 11 spaces:
-
-.
-  10.  foo
-
-           bar
-.
-
    
-
  1. foo
    
-
    bar
-
    2. 
-

-.
-
-If the *first* block in the list item is an indented code block,
-then by rule #2, the contents must be indented *one* space after the
-list marker:
-
-.
-    indented code
-
-paragraph
-
-    more code
-.
-
indented code
-

-
paragraph

-
more code
-

-.
-
-.
-1.     indented code
-
-   paragraph
-
-       more code
-.
-
    
-
  1. indented code
-
    
-
    paragraph
    
-
    more code
-
    2. 
-

-.
-
-Note that an additional space indent is interpreted as space
-inside the code block:
-
-.
-1.      indented code
-
-   paragraph
-
-       more code
-.
-
    
-
  1.  indented code
-
    
-
    paragraph
    
-
    more code
-
    2. 
-

-.
-
-Note that rules #1 and #2 only apply to two cases:  (a) cases
-in which the lines to be included in a list item begin with a nonspace
-character, and (b) cases in which they begin with an indented code
-block.  In a case like the following, where the first block begins with
-a three-space indent, the rules do not allow us to form a list item by
-indenting the whole thing and prepending a list marker:
-
-.
-   foo
-
-bar
-.
-
foo

-
bar

-.
-
-.
--    foo
-
-  bar
-.
-
    
-
  • foo
    • 
-

-
bar

-.
-
-This is not a significant restriction, because when a block begins
-with 1-3 spaces indent, the indentation can always be removed without
-a change in interpretation, allowing rule #1 to be applied.  So, in
-the above case:
-
-.
--  foo
-
-   bar
-.
-
    
-
  • foo
    
-
    bar
    • 
-

-.
-
-
-3.  **Indentation.**  If a sequence of lines *Ls* constitutes a list item
-    according to rule #1 or #2, then the result of indenting each line
-    of *L* by 1-3 spaces (the same for each line) also constitutes a
-    list item with the same contents and attributes.  If a line is
-    empty, then it need not be indented.
-
-Indented one space:
-
-.
- 1.  A paragraph
-     with two lines.
-
-         indented code
-
-     > A block quote.
-.
-
    
-
  1. A paragraph
-with two lines.
    
-
    indented code
-
    
-
    
-
    A block quote.
    
-
    2. 
-

-.
-
-Indented two spaces:
-
-.
-  1.  A paragraph
-      with two lines.
-
-          indented code
-
-      > A block quote.
-.
-
    
-
  1. A paragraph
-with two lines.
    
-
    indented code
-
    
-
    
-
    A block quote.
    
-
    2. 
-

-.
-
-Indented three spaces:
-
-.
-   1.  A paragraph
-       with two lines.
-
-           indented code
-
-       > A block quote.
-.
-
    
-
  1. A paragraph
-with two lines.
    
-
    indented code
-
    
-
    
-
    A block quote.
    
-
    2. 
-

-.
-
-Four spaces indent gives a code block:
-
-.
-    1.  A paragraph
-        with two lines.
-
-            indented code
-
-        > A block quote.
-.
-
1.  A paragraph
-    with two lines.
-
-        indented code
-
-    > A block quote.
-

-.
-
-
-4.  **Laziness.**  If a string of lines *Ls* constitute a [list
-    item](#list-item) with contents *Bs*, then the result of deleting
-    some or all of the indentation from one or more lines in which the
-    next non-space character after the indentation is
-    [paragraph continuation text](#paragraph-continuation-text) is a
-    list item with the same contents and attributes.
-
-Here is an example with lazy continuation lines:
-
-.
-  1.  A paragraph
-with two lines.
-
-          indented code
-
-      > A block quote.
-.
-
    
-
  1. A paragraph
-with two lines.
    
-
    indented code
-
    
-
    
-
    A block quote.
    
-
    2. 
-

-.
-
-Indentation can be partially deleted:
-
-.
-  1.  A paragraph
-    with two lines.
-.
-
    
-
  1. A paragraph
-with two lines.
    2. 
-

-.
-
-These examples show how laziness can work in nested structures:
-
-.
-> 1. > Blockquote
-continued here.
-.
-

-
    
-
  1. 
-
    Blockquote
-continued here.
    
-
    2. 
-

-

-.
-
-.
-> 1. > Blockquote
-> continued here.
-.
-

-
    
-
  1. 
-
    Blockquote
-continued here.
    
-
    2. 
-

-

-.
-
-
-5.  **That's all.** Nothing that is not counted as a list item by rules
-    #1--4 counts as a [list item](#list-item).
-
-The rules for sublists follow from the general rules above.  A sublist
-must be indented the same number of spaces a paragraph would need to be
-in order to be included in the list item.
-
-So, in this case we need two spaces indent:
-
-.
-- foo
-  - bar
-    - baz
-.
-
    
-
  • foo
-
      
-
    • bar
-
        
-
      • baz
        • 
-
      • 
-
    • 
-

-.
-
-One is not enough:
-
-.
-- foo
- - bar
-  - baz
-.
-
    
-
  • foo
    • 
-
  • bar
    • 
-
  • baz
    • 
-

-.
-
-Here we need four, because the list marker is wider:
-
-.
-10) foo
-    - bar
-.
-
    
-
  1. foo
-
      
-
    • bar
      • 
-
    2. 
-

-.
-
-Three is not enough:
-
-.
-10) foo
-   - bar
-.
-
    
-
  1. foo
    2. 
-

-
    
-
  • bar
    • 
-

-.
-
-A list may be the first block in a list item:
-
-.
-- - foo
-.
-
    
-
    • 
-
    • foo
      • 
-
    • 
-

-.
-
-.
-1. - 2. foo
-.
-
    
-
    1. 
-
      • 
-
      1. foo
        2. 
-
      • 
-
    2. 
-

-.
-
-A list item may be empty:
-
-.
-- foo
--
-- bar
-.
-
    
-
  • foo
    • 
-
  • 
-
  • bar
    • 
-

-.
-
-.
--
-.
-
    
-
  • 
-

-.
-
-### Motivation
-
-John Gruber's Markdown spec says the following about list items:
-
-1. "List markers typically start at the left margin, but may be indented
-   by up to three spaces. List markers must be followed by one or more
-   spaces or a tab."
-
-2. "To make lists look nice, you can wrap items with hanging indents....
-   But if you don't want to, you don't have to."
-
-3. "List items may consist of multiple paragraphs. Each subsequent
-   paragraph in a list item must be indented by either 4 spaces or one
-   tab."
-
-4. "It looks nice if you indent every line of the subsequent paragraphs,
-   but here again, Markdown will allow you to be lazy."
-
-5. "To put a blockquote within a list item, the blockquote's `>`
-   delimiters need to be indented."
-
-6. "To put a code block within a list item, the code block needs to be
-   indented twice — 8 spaces or two tabs."
-
-These rules specify that a paragraph under a list item must be indented
-four spaces (presumably, from the left margin, rather than the start of
-the list marker, but this is not said), and that code under a list item
-must be indented eight spaces instead of the usual four.  They also say
-that a block quote must be indented, but not by how much; however, the
-example given has four spaces indentation.  Although nothing is said
-about other kinds of block-level content, it is certainly reasonable to
-infer that *all* block elements under a list item, including other
-lists, must be indented four spaces.  This principle has been called the
-*four-space rule*.
-
-The four-space rule is clear and principled, and if the reference
-implementation `Markdown.pl` had followed it, it probably would have
-become the standard.  However, `Markdown.pl` allowed paragraphs and
-sublists to start with only two spaces indentation, at least on the
-outer level.  Worse, its behavior was inconsistent: a sublist of an
-outer-level list needed two spaces indentation, but a sublist of this
-sublist needed three spaces.  It is not surprising, then, that different
-implementations of Markdown have developed very different rules for
-determining what comes under a list item.  (Pandoc and python-Markdown,
-for example, stuck with Gruber's syntax description and the four-space
-rule, while discount, redcarpet, marked, PHP Markdown, and others
-followed `Markdown.pl`'s behavior more closely.)
-
-Unfortunately, given the divergences between implementations, there
-is no way to give a spec for list items that will be guaranteed not
-to break any existing documents.  However, the spec given here should
-correctly handle lists formatted with either the four-space rule or
-the more forgiving `Markdown.pl` behavior, provided they are laid out
-in a way that is natural for a human to read.
-
-The strategy here is to let the width and indentation of the list marker
-determine the indentation necessary for blocks to fall under the list
-item, rather than having a fixed and arbitrary number.  The writer can
-think of the body of the list item as a unit which gets indented to the
-right enough to fit the list marker (and any indentation on the list
-marker).  (The laziness rule, #4, then allows continuation lines to be
-unindented if needed.)
-
-This rule is superior, we claim, to any rule requiring a fixed level of
-indentation from the margin.  The four-space rule is clear but
-unnatural. It is quite unintuitive that
-
-``` markdown
-- foo
-
-  bar
-
-  - baz
-```
-
-should be parsed as two lists with an intervening paragraph,
-
-``` html
-
    
-
  • foo
    • 
-

-
bar

-
    
-
  • baz
    • 
-

-```
-
-as the four-space rule demands, rather than a single list,
-
-``` html
-
    
-
  • foo
    
-
    bar
    
-
      
-
    • baz
      • 
-
    • 
-

-```
-
-The choice of four spaces is arbitrary.  It can be learned, but it is
-not likely to be guessed, and it trips up beginners regularly.
-
-Would it help to adopt a two-space rule?  The problem is that such
-a rule, together with the rule allowing 1--3 spaces indentation of the
-initial list marker, allows text that is indented *less than* the
-original list marker to be included in the list item. For example,
-`Markdown.pl` parses
-
-``` markdown
-   - one
-
-  two
-```
-
-as a single list item, with `two` a continuation paragraph:
-
-``` html
-
    
-
  • one
    
-
    two
    • 
-

-```
-
-and similarly
-
-``` markdown
->   - one
->
->  two
-```
-
-as
-
-``` html
-

-
    
-
  • one
    
-
    two
    • 
-

-

-```
-
-This is extremely unintuitive.
-
-Rather than requiring a fixed indent from the margin, we could require
-a fixed indent (say, two spaces, or even one space) from the list marker (which
-may itself be indented).  This proposal would remove the last anomaly
-discussed.  Unlike the spec presented above, it would count the following
-as a list item with a subparagraph, even though the paragraph `bar`
-is not indented as far as the first paragraph `foo`:
-
-``` markdown
- 10. foo
-
-   bar  
-```
-
-Arguably this text does read like a list item with `bar` as a subparagraph,
-which may count in favor of the proposal.  However, on this proposal indented
-code would have to be indented six spaces after the list marker.  And this
-would break a lot of existing Markdown, which has the pattern:
-
-``` markdown
-1.  foo
-
-        indented code
-```
-
-where the code is indented eight spaces.  The spec above, by contrast, will
-parse this text as expected, since the code block's indentation is measured
-from the beginning of `foo`.
-
-The one case that needs special treatment is a list item that *starts*
-with indented code.  How much indentation is required in that case, since
-we don't have a "first paragraph" to measure from?  Rule #2 simply stipulates
-that in such cases, we require one space indentation from the list marker
-(and then the normal four spaces for the indented code).  This will match the
-four-space rule in cases where the list marker plus its initial indentation
-takes four spaces (a common case), but diverge in other cases.
-
-## Lists
-
-A [list](#list)  is a sequence of one or more
-list items [of the same type](#of-the-same-type).  The list items
-may be separated by single [blank lines](#blank-line), but two
-blank lines end all containing lists.
-
-Two list items are [of the same type](#of-the-same-type)
- if they begin with a [list
-marker](#list-marker) of the same type.  Two list markers are of the
-same type if (a) they are bullet list markers using the same character
-(`-`, `+`, or `*`) or (b) they are ordered list numbers with the same
-delimiter (either `.` or `)`).
-
-A list is an [ordered list](#ordered-list) 
-if its constituent list items begin with
-[ordered list markers](#ordered-list-marker), and a [bullet
-list](#bullet-list)  if its constituent list
-items begin with [bullet list markers](#bullet-list-marker).
-
-The [start number](#start-number) 
-of an [ordered list](#ordered-list) is determined by the list number of
-its initial list item.  The numbers of subsequent list items are
-disregarded.
-
-A list is [loose](#loose) if it any of its constituent list items are
-separated by blank lines, or if any of its constituent list items
-directly contain two block-level elements with a blank line between
-them.  Otherwise a list is [tight](#tight).  (The difference in HTML output
-is that paragraphs in a loose with are wrapped in `
` tags, while
-paragraphs in a tight list are not.)
-
-Changing the bullet or ordered list delimiter starts a new list:
-
-.
-- foo
-- bar
-+ baz
-.
-
    
-
  • foo
    • 
-
  • bar
    • 
-

-
    
-
  • baz
    • 
-

-.
-
-.
-1. foo
-2. bar
-3) baz
-.
-
    
-
  1. foo
    2. 
-
  2. bar
    3. 
-

-
    
-
  1. baz
    2. 
-

-.
-
-There can be blank lines between items, but two blank lines end
-a list:
-
-.
-- foo
-
-- bar
-
-
-- baz
-.
-
    
-
  • foo
    • 
-
  • bar
    • 
-

-
    
-
  • baz
    • 
-

-.
-
-As illustrated above in the section on [list items](#list-item),
-two blank lines between blocks *within* a list item will also end a
-list:
-
-.
-- foo
-
-
-  bar
-- baz
-.
-
    
-
  • foo
    • 
-

-
bar

-
    
-
  • baz
    • 
-

-.
-
-Indeed, two blank lines will end *all* containing lists:
-
-.
-- foo
-  - bar
-    - baz
-
-
-      bim
-.
-
    
-
  • foo
-
      
-
    • bar
-
        
-
      • baz
        • 
-
      • 
-
    • 
-

-
  bim
-

-.
-
-Thus, two blank lines can be used to separate consecutive lists of
-the same type, or to separate a list from an indented code block
-that would otherwise be parsed as a subparagraph of the final list
-item:
-
-.
-- foo
-- bar
-
-
-- baz
-- bim
-.
-
    
-
  • foo
    • 
-
  • bar
    • 
-

-
    
-
  • baz
    • 
-
  • bim
    • 
-

-.
-
-.
--   foo
-
-    notcode
-
--   foo
-
-
-    code
-.
-
    
-
  • foo
    
-
    notcode
    • 
-
  • foo
    • 
-

-
code
-

-.
-
-List items need not be indented to the same level.  The following
-list items will be treated as items at the same list level,
-since none is indented enough to belong to the previous list
-item:
-
-.
-- a
- - b
-  - c
-   - d
-  - e
- - f
-- g
-.
-
    
-
  • a
    • 
-
  • b
    • 
-
  • c
    • 
-
  • d
    • 
-
  • e
    • 
-
  • f
    • 
-
  • g
    • 
-

-.
-
-This is a loose list, because there is a blank line between
-two of the list items:
-
-.
-- a
-- b
-
-- c
-.
-
    
-
  • a
    • 
-
  • b
    • 
-
  • c
    • 
-

-.
-
-So is this, with a empty second item:
-
-.
-* a
-*
-
-* c
-.
-
    
-
  • a
    • 
-
  • 
-
  • c
    • 
-

-.
-
-These are loose lists, even though there is no space between the items,
-because one of the items directly contains two block-level elements
-with a blank line between them:
-
-.
-- a
-- b
-
-  c
-- d
-.
-
    
-
  • a
    • 
-
  • b
    
-
    c
    • 
-
  • d
    • 
-

-.
-
-.
-- a
-- b
-
-  [ref]: /url
-- d
-.
-
    
-
  • a
    • 
-
  • b
    • 
-
  • d
    • 
-

-.
-
-This is a tight list, because the blank lines are in a code block:
-
-.
-- a
-- ```
-  b
-
-
-  ```
-- c
-.
-
    
-
  • a
    • 
-
  • b
-
-
-
    • 
-
  • c
    • 
-

-.
-
-This is a tight list, because the blank line is between two
-paragraphs of a sublist.  So the inner list is loose while
-the other list is tight:
-
-.
-- a
-  - b
-
-    c
-- d
-.
-
    
-
  • a
-
      
-
    • b
      
-
      c
      • 
-
    • 
-
  • d
    • 
-

-.
-
-This is a tight list, because the blank line is inside the
-block quote:
-
-.
-* a
-  > b
-  >
-* c
-.
-
    
-
  • a
-
    
-
    b
    
-
    • 
-
  • c
    • 
-

-.
-
-This list is tight, because the consecutive block elements
-are not separated by blank lines:
-
-.
-- a
-  > b
-  ```
-  c
-  ```
-- d
-.
-
    
-
  • a
-
    
-
    b
    
-
    
-
    c
-
    • 
-
  • d
    • 
-

-.
-
-A single-paragraph list is tight:
-
-.
-- a
-.
-
    
-
  • a
    • 
-

-.
-
-.
-- a
-  - b
-.
-
    
-
  • a
-
      
-
    • b
      • 
-
    • 
-

-.
-
-Here the outer list is loose, the inner list tight:
-
-.
-* foo
-  * bar
-
-  baz
-.
-
    
-
  • foo
    
-
      
-
    • bar
      • 
-
    
-
    baz
    • 
-

-.
-
-.
-- a
-  - b
-  - c
-
-- d
-  - e
-  - f
-.
-
    
-
  • a
    
-
      
-
    • b
      • 
-
    • c
      • 
-
    • 
-
  • d
    
-
      
-
    • e
      • 
-
    • f
      • 
-
    • 
-

-.
-
-# Inlines
-
-Inlines are parsed sequentially from the beginning of the character
-stream to the end (left to right, in left-to-right languages).
-Thus, for example, in
-
-.
-`hi`lo`
-.
-
hilo`

-.
-
-`hi` is parsed as code, leaving the backtick at the end as a literal
-backtick.
-
-## Backslash escapes
-
-Any ASCII punctuation character may be backslash-escaped:
-
-.
-\!\"\#\$\%\&\'\(\)\*\+\,\-\.\/\:\;\<\=\>\?\@\[\\\]\^\_\`\{\|\}\~
-.
-
!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~

-.
-
-Backslashes before other characters are treated as literal
-backslashes:
-
-.
-\→\A\a\ \3\φ\«
-.
-
\   \A\a\ \3\φ\«

-.
-
-Escaped characters are treated as regular characters and do
-not have their usual Markdown meanings:
-
-.
-\*not emphasized*
-\
 not a tag
-\[not a link](/foo)
-\`not code`
-1\. not a list
-\* not a list
-\# not a header
-\[foo]: /url "not a reference"
-.
-
*not emphasized*
-<br/> not a tag
-[not a link](/foo)
-`not code`
-1. not a list
-* not a list
-# not a header
-[foo]: /url "not a reference"

-.
-
-If a backslash is itself escaped, the following character is not:
-
-.
-\\*emphasis*
-.
-
\emphasis

-.
-
-A backslash at the end of the line is a hard line break:
-
-.
-foo\
-bar
-.
-
foo

-bar

-.
-
-Backslash escapes do not work in code blocks, code spans, autolinks, or
-raw HTML:
-
-.
-`` \[\` ``
-.
-
\[\`

-.
-
-.
-    \[\]
-.
-
\[\]
-

-.
-
-.
-~~~
-\[\]
-~~~
-.
-
\[\]
-

-.
-
-.
-
-.
-
http://google.com?find=\*

-.
-
-.
-
-.
-

-.
-
-But they work in all other contexts, including URLs and link titles,
-link references, and info strings in [fenced code
-blocks](#fenced-code-block):
-
-.
-[foo](/bar\* "ti\*tle")
-.
-
foo

-.
-
-.
-[foo]
-
-[foo]: /bar\* "ti\*tle"
-.
-
foo

-.
-
-.
-``` foo\+bar
-foo
-```
-.
-
foo
-

-.
-
-
-## Entities
-
-With the goal of making this standard as HTML-agnostic as possible, all HTML valid HTML Entities in any
-context are recognized as such and converted into their actual values (i.e. the UTF8 characters representing
-the entity itself) before they are stored in the AST.
-
-This allows implementations that target HTML output to trivially escape the entities when generating HTML,
-and simplifies the job of implementations targetting other languages, as these will only need to handle the
-UTF8 chars and need not be HTML-entity aware.
-
-[Named entities](#name-entities)  consist of `&`
-+ any of the valid HTML5 entity names + `;`. The [following document](http://www.whatwg.org/specs/web-apps/current-work/multipage/entities.json)
-is used as an authoritative source of the valid entity names and their corresponding codepoints.
-
-Conforming implementations that target Markdown don't need to generate entities for all the valid
-named entities that exist, with the exception of `"` (`"`), `&` (`&`), `<` (`<`) and `>` (`>`),
-which always need to be written as entities for security reasons.
-
-.
-  & © Æ Ď ¾ ℋ ⅆ ∲
-.
-
  & © Æ Ď ¾ ℋ ⅆ ∲

-.
-
-[Decimal entities](#decimal-entities) 
-consist of `&#` + a string of 1--8 arabic digits + `;`. Again, these entities need to be recognised
-and tranformed into their corresponding UTF8 codepoints. Invalid Unicode codepoints will be written
-as the "unknown codepoint" character (`0xFFFD`)
-
-.
-# Ӓ Ϡ �
-.
-
# Ӓ Ϡ �

-.
-
-[Hexadecimal entities](#hexadecimal-entities) 
-consist of `&#` + either `X` or `x` + a string of 1-8 hexadecimal digits
-+ `;`. They will also be parsed and turned into their corresponding UTF8 values in the AST.
-
-.
-" ആ ಫ
-.
-
" ആ ಫ

-.
-
-Here are some nonentities:
-
-.
-  &x; &#; &#x; &ThisIsWayTooLongToBeAnEntityIsntIt; &hi?;
-.
-
&nbsp &x; &#; &#x; &ThisIsWayTooLongToBeAnEntityIsntIt; &hi?;

-.
-
-Although HTML5 does accept some entities without a trailing semicolon
-(such as `©`), these are not recognized as entities here, because it makes the grammar too ambiguous:
-
-.
-©
-.
-
&copy

-.
-
-Strings that are not on the list of HTML5 named entities are not recognized as entities either:
-
-.
-&MadeUpEntity;
-.
-
&MadeUpEntity;

-.
-
-Entities are recognized in any context besides code spans or
-code blocks, including raw HTML, URLs, [link titles](#link-title), and
-[fenced code block](#fenced-code-block) info strings:
-
-.
-
-.
-

-.
-
-.
-[foo](/föö "föö")
-.
-
foo

-.
-
-.
-[foo]
-
-[foo]: /föö "föö"
-.
-
foo

-.
-
-.
-``` föö
-foo
-```
-.
-
foo
-

-.
-
-Entities are treated as literal text in code spans and code blocks:
-
-.
-`föö`
-.
-
f&ouml;&ouml;

-.
-
-.
-    föfö
-.
-
f&ouml;f&ouml;
-

-.
-
-## Code span
-
-A [backtick string](#backtick-string) 
-is a string of one or more backtick characters (`` ` ``) that is neither
-preceded nor followed by a backtick.
-
-A code span begins with a backtick string and ends with a backtick
-string of equal length.  The contents of the code span are the
-characters between the two backtick strings, with leading and trailing
-spaces and newlines removed, and consecutive spaces and newlines
-collapsed to single spaces.
-
-This is a simple code span:
-
-.
-`foo`
-.
-
foo

-.
-
-Here two backticks are used, because the code contains a backtick.
-This example also illustrates stripping of leading and trailing spaces:
-
-.
-`` foo ` bar  ``
-.
-
foo ` bar

-.
-
-This example shows the motivation for stripping leading and trailing
-spaces:
-
-.
-` `` `
-.
-
``

-.
-
-Newlines are treated like spaces:
-
-.
-``
-foo
-``
-.
-
foo

-.
-
-Interior spaces and newlines are collapsed into single spaces, just
-as they would be by a browser:
-
-.
-`foo   bar
-  baz`
-.
-
foo bar baz

-.
-
-Q: Why not just leave the spaces, since browsers will collapse them
-anyway?  A:  Because we might be targeting a non-HTML format, and we
-shouldn't rely on HTML-specific rendering assumptions.
-
-(Existing implementations differ in their treatment of internal
-spaces and newlines.  Some, including `Markdown.pl` and
-`showdown`, convert an internal newline into a `
` tag.
-But this makes things difficult for those who like to hard-wrap
-their paragraphs, since a line break in the midst of a code
-span will cause an unintended line break in the output.  Others
-just leave internal spaces as they are, which is fine if only
-HTML is being targeted.)
-
-.
-`foo `` bar`
-.
-
foo `` bar

-.
-
-Note that backslash escapes do not work in code spans. All backslashes
-are treated literally:
-
-.
-`foo\`bar`
-.
-
foo\bar`

-.
-
-Backslash escapes are never needed, because one can always choose a
-string of *n* backtick characters as delimiters, where the code does
-not contain any strings of exactly *n* backtick characters.
-
-Code span backticks have higher precedence than any other inline
-constructs except HTML tags and autolinks.  Thus, for example, this is
-not parsed as emphasized text, since the second `*` is part of a code
-span:
-
-.
-*foo`*`
-.
-
*foo*

-.
-
-And this is not parsed as a link:
-
-.
-[not a `link](/foo`)
-.
-
[not a link](/foo)

-.
-
-But this is a link:
-
-.
-`
-.
-
http://foo.bar.`baz`

-.
-
-And this is an HTML tag:
-
-.
-`
-.
-
`

-.
-
-When a backtick string is not closed by a matching backtick string,
-we just have literal backticks:
-
-.
-```foo``
-.
-
```foo``

-.
-
-.
-`foo
-.
-
`foo

-.
-
-## Emphasis and strong emphasis
-
-John Gruber's original [Markdown syntax
-description](http://daringfireball.net/projects/markdown/syntax#em) says:
-
-> Markdown treats asterisks (`*`) and underscores (`_`) as indicators of
-> emphasis. Text wrapped with one `*` or `_` will be wrapped with an HTML
-> `` tag; double `*`'s or `_`'s will be wrapped with an HTML ``
-> tag.
-
-This is enough for most users, but these rules leave much undecided,
-especially when it comes to nested emphasis.  The original
-`Markdown.pl` test suite makes it clear that triple `***` and
-`___` delimiters can be used for strong emphasis, and most
-implementations have also allowed the following patterns:
-
-``` markdown
-***strong emph***
-***strong** in emph*
-***emph* in strong**
-**in strong *emph***
-*in emph **strong***
-```
-
-The following patterns are less widely supported, but the intent
-is clear and they are useful (especially in contexts like bibliography
-entries):
-
-``` markdown
-*emph *with emph* in it*
-**strong **with strong** in it**
-```
-
-Many implementations have also restricted intraword emphasis to
-the `*` forms, to avoid unwanted emphasis in words containing
-internal underscores.  (It is best practice to put these in code
-spans, but users often do not.)
-
-``` markdown
-internal emphasis: foo*bar*baz
-no emphasis: foo_bar_baz
-```
-
-The following rules capture all of these patterns, while allowing
-for efficient parsing strategies that do not backtrack:
-
-1.  A single `*` character [can open emphasis](#can-open-emphasis)
-     iff
-
-    (a) it is not part of a sequence of four or more unescaped `*`s,
-    (b) it is not followed by whitespace, and
-    (c) either it is not followed by a `*` character or it is
-        followed immediately by strong emphasis.
-
-2.  A single `_` character [can open emphasis](#can-open-emphasis) iff
-
-    (a) it is not part of a sequence of four or more unescaped `_`s,
-    (b) it is not followed by whitespace,
-    (c) it is not preceded by an ASCII alphanumeric character, and
-    (d) either it is not followed by a `_` character or it is
-        followed immediately by strong emphasis.
-
-3.  A single `*` character [can close emphasis](#can-close-emphasis)
-     iff
-
-    (a) it is not part of a sequence of four or more unescaped `*`s, and
-    (b) it is not preceded by whitespace.
-
-4.  A single `_` character [can close emphasis](#can-close-emphasis) iff
-
-    (a) it is not part of a sequence of four or more unescaped `_`s,
-    (b) it is not preceded by whitespace, and
-    (c) it is not followed by an ASCII alphanumeric character.
-
-5.  A double `**` [can open strong emphasis](#can-open-strong-emphasis)
-     iff
-
-    (a) it is not part of a sequence of four or more unescaped `*`s,
-    (b) it is not followed by whitespace, and
-    (c) either it is not followed by a `*` character or it is
-        followed immediately by emphasis.
-
-6.  A double `__` [can open strong emphasis](#can-open-strong-emphasis)
-    iff
-
-    (a) it is not part of a sequence of four or more unescaped `_`s,
-    (b) it is not followed by whitespace, and
-    (c) it is not preceded by an ASCII alphanumeric character, and
-    (d) either it is not followed by a `_` character or it is
-        followed immediately by emphasis.
-
-7.  A double `**` [can close strong emphasis](#can-close-strong-emphasis)
-     iff
-
-    (a) it is not part of a sequence of four or more unescaped `*`s, and
-    (b) it is not preceded by whitespace.
-
-8.  A double `__` [can close strong emphasis](#can-close-strong-emphasis)
-    iff
-
-    (a) it is not part of a sequence of four or more unescaped `_`s,
-    (b) it is not preceded by whitespace, and
-    (c) it is not followed by an ASCII alphanumeric character.
-
-9.  Emphasis begins with a delimiter that [can open
-    emphasis](#can-open-emphasis) and includes inlines parsed
-    sequentially until a delimiter that [can close
-    emphasis](#can-close-emphasis), and that uses the same
-    character (`_` or `*`) as the opening delimiter, is reached.
-
-10. Strong emphasis begins with a delimiter that [can open strong
-    emphasis](#can-open-strong-emphasis) and includes inlines parsed
-    sequentially until a delimiter that [can close strong
-    emphasis](#can-close-strong-emphasis), and that uses the
-    same character (`_` or `*`) as the opening delimiter, is reached.
-
-These rules can be illustrated through a series of examples.
-
-Simple emphasis:
-
-.
-*foo bar*
-.
-
foo bar

-.
-
-.
-_foo bar_
-.
-
foo bar

-.
-
-Simple strong emphasis:
-
-.
-**foo bar**
-.
-
foo bar

-.
-
-.
-__foo bar__
-.
-
foo bar

-.
-
-Emphasis can continue over line breaks:
-
-.
-*foo
-bar*
-.
-
foo
-bar

-.
-
-.
-_foo
-bar_
-.
-
foo
-bar

-.
-
-.
-**foo
-bar**
-.
-
foo
-bar

-.
-
-.
-__foo
-bar__
-.
-
foo
-bar

-.
-
-Emphasis can contain other inline constructs:
-
-.
-*foo [bar](/url)*
-.
-
foo bar

-.
-
-.
-_foo [bar](/url)_
-.
-
foo bar

-.
-
-.
-**foo [bar](/url)**
-.
-
foo bar

-.
-
-.
-__foo [bar](/url)__
-.
-
foo bar

-.
-
-Symbols contained in other inline constructs will not
-close emphasis:
-
-.
-*foo [bar*](/url)
-.
-
*foo bar*

-.
-
-.
-_foo [bar_](/url)
-.
-
_foo bar_

-.
-
-.
-**
-.
-
**

-.
-
-.
-__
-.
-
__

-.
-
-.
-*a `*`*
-.
-
a *

-.
-
-.
-_a `_`_
-.
-
a _

-.
-
-.
-**a
-.
-
**ahttp://foo.bar?q=**

-.
-
-.
-__a
-.
-
__ahttp://foo.bar?q=__

-.
-
-This is not emphasis, because the opening delimiter is
-followed by white space:
-
-.
-and * foo bar*
-.
-
and * foo bar*

-.
-
-.
-_ foo bar_
-.
-
_ foo bar_

-.
-
-.
-and ** foo bar**
-.
-
and ** foo bar**

-.
-
-.
-__ foo bar__
-.
-
__ foo bar__

-.
-
-This is not emphasis, because the closing delimiter is
-preceded by white space:
-
-.
-and *foo bar *
-.
-
and *foo bar *

-.
-
-.
-and _foo bar _
-.
-
and _foo bar _

-.
-
-.
-and **foo bar **
-.
-
and **foo bar **

-.
-
-.
-and __foo bar __
-.
-
and __foo bar __

-.
-
-The rules imply that a sequence of four or more unescaped `*` or
-`_` characters will always be parsed as a literal string:
-
-.
-****hi****
-.
-
****hi****

-.
-
-.
-_____hi_____
-.
-
_____hi_____

-.
-
-.
-Sign here: _________
-.
-
Sign here: _________

-.
-
-The rules also imply that there can be no empty emphasis or strong
-emphasis:
-
-.
-** is not an empty emphasis
-.
-
** is not an empty emphasis

-.
-
-.
-**** is not an empty strong emphasis
-.
-
**** is not an empty strong emphasis

-.
-
-To include `*` or `_` in emphasized sections, use backslash escapes
-or code spans:
-
-.
-*here is a \**
-.
-
here is a *

-.
-
-.
-__this is a double underscore (`__`)__
-.
-
this is a double underscore (__)

-.
-
-`*` delimiters allow intra-word emphasis; `_` delimiters do not:
-
-.
-foo*bar*baz
-.
-
foobarbaz

-.
-
-.
-foo_bar_baz
-.
-
foo_bar_baz

-.
-
-.
-foo__bar__baz
-.
-
foo__bar__baz

-.
-
-.
-_foo_bar_baz_
-.
-
foo_bar_baz

-.
-
-.
-11*15*32
-.
-
111532

-.
-
-.
-11_15_32
-.
-
11_15_32

-.
-
-Internal underscores will be ignored in underscore-delimited
-emphasis:
-
-.
-_foo_bar_baz_
-.
-
foo_bar_baz

-.
-
-.
-__foo__bar__baz__
-.
-
foo__bar__baz

-.
-
-The rules are sufficient for the following nesting patterns:
-
-.
-***foo bar***
-.
-
foo bar

-.
-
-.
-___foo bar___
-.
-
foo bar

-.
-
-.
-***foo** bar*
-.
-
foo bar

-.
-
-.
-___foo__ bar_
-.
-
foo bar

-.
-
-.
-***foo* bar**
-.
-
foo bar

-.
-
-.
-___foo_ bar__
-.
-
foo bar

-.
-
-.
-*foo **bar***
-.
-
foo bar

-.
-
-.
-_foo __bar___
-.
-
foo bar

-.
-
-.
-**foo *bar***
-.
-
foo bar

-.
-
-.
-__foo _bar___
-.
-
foo bar

-.
-
-.
-*foo **bar***
-.
-
foo bar

-.
-
-.
-_foo __bar___
-.
-
foo bar

-.
-
-.
-*foo *bar* baz*
-.
-
foo bar baz

-.
-
-.
-_foo _bar_ baz_
-.
-
foo bar baz

-.
-
-.
-**foo **bar** baz**
-.
-
foo bar baz

-.
-
-.
-__foo __bar__ baz__
-.
-
foo bar baz

-.
-
-.
-*foo **bar** baz*
-.
-
foo bar baz

-.
-
-.
-_foo __bar__ baz_
-.
-
foo bar baz

-.
-
-.
-**foo *bar* baz**
-.
-
foo bar baz

-.
-
-.
-__foo _bar_ baz__
-.
-
foo bar baz

-.
-
-Note that you cannot nest emphasis directly inside emphasis
-using the same delimeter, or strong emphasis directly inside
-strong emphasis:
-
-.
-**foo**
-.
-
foo

-.
-
-.
-****foo****
-.
-
****foo****

-.
-
-For these nestings, you need to switch delimiters:
-
-.
-*_foo_*
-.
-
foo

-.
-
-.
-**__foo__**
-.
-
foo

-.
-
-Note that a `*` followed by a `*` can close emphasis, and
-a `**` followed by a `*` can close strong emphasis (and
-similarly for `_` and `__`):
-
-.
-*foo**
-.
-
foo*

-.
-
-.
-*foo *bar**
-.
-
foo bar

-.
-
-.
-**foo***
-.
-
foo*

-.
-
-.
-***foo* bar***
-.
-
foo bar*

-.
-
-.
-***foo** bar***
-.
-
foo bar**

-.
-
-The following contains no strong emphasis, because the opening
-delimiter is closed by the first `*` before `bar`:
-
-.
-*foo**bar***
-.
-
foobar**

-.
-
-However, a string of four or more `****` can never close emphasis:
-
-.
-*foo****
-.
-
*foo****

-.
-
-Note that there are some asymmetries here:
-
-.
-*foo**
-
-**foo*
-.
-
foo*

-
**foo*

-.
-
-.
-*foo *bar**
-
-**foo* bar*
-.
-
foo bar

-
**foo* bar*

-.
-
-More cases with mismatched delimiters:
-
-.
-**foo* bar*
-.
-
**foo* bar*

-.
-
-.
-*bar***
-.
-
bar**

-.
-
-.
-***foo*
-.
-
***foo*

-.
-
-.
-**bar***
-.
-
bar*

-.
-
-.
-***foo**
-.
-
***foo**

-.
-
-.
-***foo *bar*
-.
-
***foo bar

-.
-
-## Links
-
-A link contains a [link label](#link-label) (the visible text),
-a [destination](#destination) (the URI that is the link destination),
-and optionally a [link title](#link-title).  There are two basic kinds
-of links in Markdown.  In [inline links](#inline-links) the destination
-and title are given immediately after the label.  In [reference
-links](#reference-links) the destination and title are defined elsewhere
-in the document.
-
-A [link label](#link-label)   consists of
-
-- an opening `[`, followed by
-- zero or more backtick code spans, autolinks, HTML tags, link labels,
-  backslash-escaped ASCII punctuation characters, or non-`]` characters,
-  followed by
-- a closing `]`.
-
-These rules are motivated by the following intuitive ideas:
-
-- A link label is a container for inline elements.
-- The square brackets bind more tightly than emphasis markers,
-  but less tightly than `<>` or `` ` ``.
-- Link labels may contain material in matching square brackets.
-
-A [link destination](#link-destination) 
-consists of either
-
-- a sequence of zero or more characters between an opening `<` and a
-  closing `>` that contains no line breaks or unescaped `<` or `>`
-  characters, or
-
-- a nonempty sequence of characters that does not include
-  ASCII space or control characters, and includes parentheses
-  only if (a) they are backslash-escaped or (b) they are part of
-  a balanced pair of unescaped parentheses that is not itself
-  inside a balanced pair of unescaped paretheses.
-
-A [link title](#link-title)   consists of either
-
-- a sequence of zero or more characters between straight double-quote
-  characters (`"`), including a `"` character only if it is
-  backslash-escaped, or
-
-- a sequence of zero or more characters between straight single-quote
-  characters (`'`), including a `'` character only if it is
-  backslash-escaped, or
-
-- a sequence of zero or more characters between matching parentheses
-  (`(...)`), including a `)` character only if it is backslash-escaped.
-
-An [inline link](#inline-link) 
-consists of a [link label](#link-label) followed immediately
-by a left parenthesis `(`, optional whitespace,
-an optional [link destination](#link-destination),
-an optional [link title](#link-title) separated from the link
-destination by whitespace, optional whitespace, and a right
-parenthesis `)`.  The link's text consists of the label (excluding
-the enclosing square brackets) parsed as inlines.  The link's
-URI consists of the link destination, excluding enclosing `<...>` if
-present, with backslash-escapes in effect as described above.  The
-link's title consists of the link title, excluding its enclosing
-delimiters, with backslash-escapes in effect as described above.
-
-Here is a simple inline link:
-
-.
-[link](/uri "title")
-.
-
link

-.
-
-The title may be omitted:
-
-.
-[link](/uri)
-.
-
link

-.
-
-Both the title and the destination may be omitted:
-
-.
-[link]()
-.
-
link

-.
-
-.
-[link](<>)
-.
-
link

-.
-
-
-If the destination contains spaces, it must be enclosed in pointy
-braces:
-
-.
-[link](/my uri)
-.
-
[link](/my uri)

-.
-
-.
-[link]()
-.
-
link

-.
-
-The destination cannot contain line breaks, even with pointy braces:
-
-.
-[link](foo
-bar)
-.
-
[link](foo
-bar)

-.
-
-One level of balanced parentheses is allowed without escaping:
-
-.
-[link]((foo)and(bar))
-.
-
link

-.
-
-However, if you have parentheses within parentheses, you need to escape
-or use the `<...>` form:
-
-.
-[link](foo(and(bar)))
-.
-
[link](foo(and(bar)))

-.
-
-.
-[link](foo(and\(bar\)))
-.
-
link

-.
-
-.
-[link]()
-.
-
link

-.
-
-Parentheses and other symbols can also be escaped, as usual
-in Markdown:
-
-.
-[link](foo\)\:)
-.
-
link

-.
-
-URL-escaping and should be left alone inside the destination, as all URL-escaped characters
-are also valid URL characters. HTML entities in the destination will be parsed into their UTF8
-codepoints, as usual, and optionally URL-escaped when written as HTML.
-
-.
-[link](foo%20bä)
-.
-
link

-.
-
-Note that, because titles can often be parsed as destinations,
-if you try to omit the destination and keep the title, you'll
-get unexpected results:
-
-.
-[link]("title")
-.
-
link

-.
-
-Titles may be in single quotes, double quotes, or parentheses:
-
-.
-[link](/url "title")
-[link](/url 'title')
-[link](/url (title))
-.
-
link
-link
-link

-.
-
-Backslash escapes and entities may be used in titles:
-
-.
-[link](/url "title \""")
-.
-
link

-.
-
-Nested balanced quotes are not allowed without escaping:
-
-.
-[link](/url "title "and" title")
-.
-
[link](/url "title "and" title")

-.
-
-But it is easy to work around this by using a different quote type:
-
-.
-[link](/url 'title "and" title')
-.
-
link

-.
-
-(Note:  `Markdown.pl` did allow double quotes inside a double-quoted
-title, and its test suite included a test demonstrating this.
-But it is hard to see a good rationale for the extra complexity this
-brings, since there are already many ways---backslash escaping,
-entities, or using a different quote type for the enclosing title---to
-write titles containing double quotes.  `Markdown.pl`'s handling of
-titles has a number of other strange features.  For example, it allows
-single-quoted titles in inline links, but not reference links.  And, in
-reference links but not inline links, it allows a title to begin with
-`"` and end with `)`.  `Markdown.pl` 1.0.1 even allows titles with no closing
-quotation mark, though 1.0.2b8 does not.  It seems preferable to adopt
-a simple, rational rule that works the same way in inline links and
-link reference definitions.)
-
-Whitespace is allowed around the destination and title:
-
-.
-[link](   /uri
-  "title"  )
-.
-
link

-.
-
-But it is not allowed between the link label and the
-following parenthesis:
-
-.
-[link] (/uri)
-.
-
[link] (/uri)

-.
-
-Note that this is not a link, because the closing `]` occurs in
-an HTML tag:
-
-.
-[foo 
-.
-
[foo 

-.
-
-
-There are three kinds of [reference links](#reference-link):
-
-
-A [full reference link](#full-reference-link) 
-consists of a [link label](#link-label), optional whitespace, and
-another [link label](#link-label) that [matches](#matches) a
-[link reference definition](#link-reference-definition) elsewhere in the
-document.
-
-One label [matches](#matches) 
-another just in case their normalized forms are equal.  To normalize a
-label, perform the *unicode case fold* and collapse consecutive internal
-whitespace to a single space.  If there are multiple matching reference
-link definitions, the one that comes first in the document is used.  (It
-is desirable in such cases to emit a warning.)
-
-The contents of the first link label are parsed as inlines, which are
-used as the link's text.  The link's URI and title are provided by the
-matching [link reference definition](#link-reference-definition).
-
-Here is a simple example:
-
-.
-[foo][bar]
-
-[bar]: /url "title"
-.
-
foo

-.
-
-The first label can contain inline content:
-
-.
-[*foo\!*][bar]
-
-[bar]: /url "title"
-.
-
foo!

-.
-
-Matching is case-insensitive:
-
-.
-[foo][BaR]
-
-[bar]: /url "title"
-.
-
foo

-.
-
-Unicode case fold is used:
-
-.
-[Толпой][Толпой] is a Russian word.
-
-[ТОЛПОЙ]: /url
-.
-
Толпой is a Russian word.

-.
-
-Consecutive internal whitespace is treated as one space for
-purposes of determining matching:
-
-.
-[Foo
-  bar]: /url
-
-[Baz][Foo bar]
-.
-
Baz

-.
-
-There can be whitespace between the two labels:
-
-.
-[foo] [bar]
-
-[bar]: /url "title"
-.
-
foo

-.
-
-.
-[foo]
-[bar]
-
-[bar]: /url "title"
-.
-
foo

-.
-
-When there are multiple matching [link reference
-definitions](#link-reference-definition), the first is used:
-
-.
-[foo]: /url1
-
-[foo]: /url2
-
-[bar][foo]
-.
-
bar

-.
-
-Note that matching is performed on normalized strings, not parsed
-inline content.  So the following does not match, even though the
-labels define equivalent inline content:
-
-.
-[bar][foo\!]
-
-[foo!]: /url
-.
-
[bar][foo!]

-.
-
-A [collapsed reference link](#collapsed-reference-link)
- consists of a [link
-label](#link-label) that [matches](#matches) a [link reference
-definition](#link-reference-definition) elsewhere in the
-document, optional whitespace, and the string `[]`.  The contents of the
-first link label are parsed as inlines, which are used as the link's
-text.  The link's URI and title are provided by the matching reference
-link definition.  Thus, `[foo][]` is equivalent to `[foo][foo]`.
-
-.
-[foo][]
-
-[foo]: /url "title"
-.
-
foo

-.
-
-.
-[*foo* bar][]
-
-[*foo* bar]: /url "title"
-.
-
foo bar

-.
-
-The link labels are case-insensitive:
-
-.
-[Foo][]
-
-[foo]: /url "title"
-.
-
Foo

-.
-
-
-As with full reference links, whitespace is allowed
-between the two sets of brackets:
-
-.
-[foo] 
-[]
-
-[foo]: /url "title"
-.
-
foo

-.
-
-A [shortcut reference link](#shortcut-reference-link)
- consists of a [link
-label](#link-label) that [matches](#matches) a [link reference
-definition](#link-reference-definition)  elsewhere in the
-document and is not followed by `[]` or a link label.
-The contents of the first link label are parsed as inlines,
-which are used as the link's text.  the link's URI and title
-are provided by the matching link reference definition.
-Thus, `[foo]` is equivalent to `[foo][]`.
-
-.
-[foo]
-
-[foo]: /url "title"
-.
-
foo

-.
-
-.
-[*foo* bar]
-
-[*foo* bar]: /url "title"
-.
-
foo bar

-.
-
-.
-[[*foo* bar]]
-
-[*foo* bar]: /url "title"
-.
-
[foo bar]

-.
-
-The link labels are case-insensitive:
-
-.
-[Foo]
-
-[foo]: /url "title"
-.
-
Foo

-.
-
-If you just want bracketed text, you can backslash-escape the
-opening bracket to avoid links:
-
-.
-\[foo]
-
-[foo]: /url "title"
-.
-
[foo]

-.
-
-Note that this is a link, because link labels bind more tightly
-than emphasis:
-
-.
-[foo*]: /url
-
-*[foo*]
-.
-
*foo*

-.
-
-However, this is not, because link labels bind less
-tightly than code backticks:
-
-.
-[foo`]: /url
-
-[foo`]`
-.
-
[foo]

-.
-
-Link labels can contain matched square brackets:
-
-.
-[[[foo]]]
-
-[[[foo]]]: /url
-.
-
[[foo]]

-.
-
-.
-[[[foo]]]
-
-[[[foo]]]: /url1
-[foo]: /url2
-.
-
[[foo]]

-.
-
-For non-matching brackets, use backslash escapes:
-
-.
-[\[foo]
-
-[\[foo]: /url
-.
-
[foo

-.
-
-Full references take precedence over shortcut references:
-
-.
-[foo][bar]
-
-[foo]: /url1
-[bar]: /url2
-.
-
foo

-.
-
-In the following case `[bar][baz]` is parsed as a reference,
-`[foo]` as normal text:
-
-.
-[foo][bar][baz]
-
-[baz]: /url
-.
-
[foo]bar

-.
-
-Here, though, `[foo][bar]` is parsed as a reference, since
-`[bar]` is defined:
-
-.
-[foo][bar][baz]
-
-[baz]: /url1
-[bar]: /url2
-.
-
foobaz

-.
-
-Here `[foo]` is not parsed as a shortcut reference, because it
-is followed by a link label (even though `[bar]` is not defined):
-
-.
-[foo][bar][baz]
-
-[baz]: /url1
-[foo]: /url2
-.
-
[foo]bar

-.
-
-
-## Images
-
-An (unescaped) exclamation mark (`!`) followed by a reference or
-inline link will be parsed as an image.  The link label will be
-used as the image's alt text, and the link title, if any, will
-be used as the image's title.
-
-.
-![foo](/url "title")
-.
-
foo

-.
-
-.
-![foo *bar*]
-
-[foo *bar*]: train.jpg "train & tracks"
-.
-
foo <em>bar</em>

-.
-
-.
-![foo *bar*][]
-
-[foo *bar*]: train.jpg "train & tracks"
-.
-
foo <em>bar</em>

-.
-
-.
-![foo *bar*][foobar]
-
-[FOOBAR]: train.jpg "train & tracks"
-.
-
foo <em>bar</em>

-.
-
-.
-![foo](train.jpg)
-.
-
foo

-.
-
-.
-My ![foo bar](/path/to/train.jpg  "title"   )
-.
-
My foo bar

-.
-
-.
-![foo]()
-.
-
foo

-.
-
-.
-![](/url)
-.
-

-.
-
-Reference-style:
-
-.
-![foo] [bar]
-
-[bar]: /url
-.
-
foo

-.
-
-.
-![foo] [bar]
-
-[BAR]: /url
-.
-
foo

-.
-
-Collapsed:
-
-.
-![foo][]
-
-[foo]: /url "title"
-.
-
foo

-.
-
-.
-![*foo* bar][]
-
-[*foo* bar]: /url "title"
-.
-
<em>foo</em> bar

-.
-
-The labels are case-insensitive:
-
-.
-![Foo][]
-
-[foo]: /url "title"
-.
-
Foo

-.
-
-As with full reference links, whitespace is allowed
-between the two sets of brackets:
-
-.
-![foo] 
-[]
-
-[foo]: /url "title"
-.
-
foo

-.
-
-Shortcut:
-
-.
-![foo]
-
-[foo]: /url "title"
-.
-
foo

-.
-
-.
-![*foo* bar]
-
-[*foo* bar]: /url "title"
-.
-
<em>foo</em> bar

-.
-
-.
-![[foo]]
-
-[[foo]]: /url "title"
-.
-
[foo]

-.
-
-The link labels are case-insensitive:
-
-.
-![Foo]
-
-[foo]: /url "title"
-.
-
Foo

-.
-
-If you just want bracketed text, you can backslash-escape the
-opening `!` and `[`:
-
-.
-\!\[foo]
-
-[foo]: /url "title"
-.
-
![foo]

-.
-
-If you want a link after a literal `!`, backslash-escape the
-`!`:
-
-.
-\![foo]
-
-[foo]: /url "title"
-.
-
!foo

-.
-
-## Autolinks
-
-Autolinks are absolute URIs and email addresses inside `<` and `>`.
-They are parsed as links, with the URL or email address as the link
-label.
-
-A [URI autolink](#uri-autolink) 
-consists of `<`, followed by an [absolute
-URI](#absolute-uri) not containing `<`, followed by `>`.  It is parsed
-as a link to the URI, with the URI as the link's label.
-
-An [absolute URI](#absolute-uri), 
-for these purposes, consists of a [scheme](#scheme) followed by a colon (`:`)
-followed by zero or more characters other than ASCII whitespace and
-control characters, `<`, and `>`.  If the URI includes these characters,
-you must use percent-encoding (e.g. `%20` for a space).
-
-The following [schemes](#scheme) 
-are recognized (case-insensitive):
-`coap`, `doi`, `javascript`, `aaa`, `aaas`, `about`, `acap`, `cap`,
-`cid`, `crid`, `data`, `dav`, `dict`, `dns`, `file`, `ftp`, `geo`, `go`,
-`gopher`, `h323`, `http`, `https`, `iax`, `icap`, `im`, `imap`, `info`,
-`ipp`, `iris`, `iris.beep`, `iris.xpc`, `iris.xpcs`, `iris.lwz`, `ldap`,
-`mailto`, `mid`, `msrp`, `msrps`, `mtqp`, `mupdate`, `news`, `nfs`,
-`ni`, `nih`, `nntp`, `opaquelocktoken`, `pop`, `pres`, `rtsp`,
-`service`, `session`, `shttp`, `sieve`, `sip`, `sips`, `sms`, `snmp`,`
-soap.beep`, `soap.beeps`, `tag`, `tel`, `telnet`, `tftp`, `thismessage`,
-`tn3270`, `tip`, `tv`, `urn`, `vemmi`, `ws`, `wss`, `xcon`,
-`xcon-userid`, `xmlrpc.beep`, `xmlrpc.beeps`, `xmpp`, `z39.50r`,
-`z39.50s`, `adiumxtra`, `afp`, `afs`, `aim`, `apt`,` attachment`, `aw`,
-`beshare`, `bitcoin`, `bolo`, `callto`, `chrome`,` chrome-extension`,
-`com-eventbrite-attendee`, `content`, `cvs`,` dlna-playsingle`,
-`dlna-playcontainer`, `dtn`, `dvb`, `ed2k`, `facetime`, `feed`,
-`finger`, `fish`, `gg`, `git`, `gizmoproject`, `gtalk`, `hcp`, `icon`,
-`ipn`, `irc`, `irc6`, `ircs`, `itms`, `jar`, `jms`, `keyparc`, `lastfm`,
-`ldaps`, `magnet`, `maps`, `market`,` message`, `mms`, `ms-help`,
-`msnim`, `mumble`, `mvn`, `notes`, `oid`, `palm`, `paparazzi`,
-`platform`, `proxy`, `psyc`, `query`, `res`, `resource`, `rmi`, `rsync`,
-`rtmp`, `secondlife`, `sftp`, `sgn`, `skype`, `smb`, `soldat`,
-`spotify`, `ssh`, `steam`, `svn`, `teamspeak`, `things`, `udp`,
-`unreal`, `ut2004`, `ventrilo`, `view-source`, `webcal`, `wtai`,
-`wyciwyg`, `xfire`, `xri`, `ymsgr`.
-
-Here are some valid autolinks:
-
-.
-
-.
-
http://foo.bar.baz

-.
-
-.
-
-.
-
http://foo.bar.baz?q=hello&id=22&boolean

-.
-
-.
-
-.
-
irc://foo.bar:2233/baz

-.
-
-Uppercase is also fine:
-
-.
-
-.
-
MAILTO:FOO@BAR.BAZ

-.
-
-Spaces are not allowed in autolinks:
-
-.
-
-.
-
<http://foo.bar/baz bim>

-.
-
-An [email autolink](#email-autolink) 
-consists of `<`, followed by an [email address](#email-address),
-followed by `>`.  The link's label is the email address,
-and the URL is `mailto:` followed by the email address.
-
-An [email address](#email-address), 
-for these purposes, is anything that matches
-the [non-normative regex from the HTML5
-spec](http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#e-mail-state-%28type=email%29):
-
-    /^[a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]+@[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?
-    (?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*$/
-
-Examples of email autolinks:
-
-.
-
-.
-
foo@bar.baz.com

-.
-
-.
-
-.
-
foo+special@Bar.baz-bar0.com

-.
-
-These are not autolinks:
-
-.
-<>
-.
-
<>

-.
-
-.
-
-.
-
<heck://bing.bong>

-.
-
-.
-< http://foo.bar >
-.
-
< http://foo.bar >

-.
-
-.
-
-.
-
<foo.bar.baz>

-.
-
-.
-
-.
-
<localhost:5001/foo>

-.
-
-.
-http://google.com
-.
-
http://google.com

-.
-
-.
-foo@bar.baz.com
-.
-
foo@bar.baz.com

-.
-
-## Raw HTML
-
-Text between `<` and `>` that looks like an HTML tag is parsed as a
-raw HTML tag and will be rendered in HTML without escaping.
-Tag and attribute names are not limited to current HTML tags,
-so custom tags (and even, say, DocBook tags) may be used.
-
-Here is the grammar for tags:
-
-A [tag name](#tag-name)  consists of an ASCII letter
-followed by zero or more ASCII letters or digits.
-
-An [attribute](#attribute)  consists of whitespace,
-an **attribute name**, and an optional **attribute value
-specification**.
-
-An [attribute name](#attribute-name) 
-consists of an ASCII letter, `_`, or `:`, followed by zero or more ASCII
-letters, digits, `_`, `.`, `:`, or `-`.  (Note:  This is the XML
-specification restricted to ASCII.  HTML5 is laxer.)
-
-An [attribute value specification](#attribute-value-specification)
- consists of optional whitespace,
-a `=` character, optional whitespace, and an [attribute
-value](#attribute-value).
-
-An [attribute value](#attribute-value) 
-consists of an [unquoted attribute value](#unquoted-attribute-value),
-a [single-quoted attribute value](#single-quoted-attribute-value),
-or a [double-quoted attribute value](#double-quoted-attribute-value).
-
-An [unquoted attribute value](#unquoted-attribute-value)
- is a nonempty string of characters not
-including spaces, `"`, `'`, `=`, `<`, `>`, or `` ` ``.
-
-A [single-quoted attribute value](#single-quoted-attribute-value)
- consists of `'`, zero or more
-characters not including `'`, and a final `'`.
-
-A [double-quoted attribute value](#double-quoted-attribute-value)
- consists of `"`, zero or more
-characters not including `"`, and a final `"`.
-
-An [open tag](#open-tag)  consists of a `<` character,
-a [tag name](#tag-name), zero or more [attributes](#attribute),
-optional whitespace, an optional `/` character, and a `>` character.
-
-A [closing tag](#closing-tag)  consists of the
-string ``.
-
-An [HTML comment](#html-comment)  consists of the
-string ``.
-
-A [processing instruction](#processing-instruction)
- consists of the string ``, and the string
-`?>`.
-
-A [declaration](#declaration)  consists of the
-string ``, and
-the character `>`.
-
-A [CDATA section](#cdata-section)  consists of
-the string ``, and the string `]]>`.
-
-An [HTML tag](#html-tag)  consists of an [open
-tag](#open-tag), a [closing tag](#closing-tag), an [HTML
-comment](#html-comment), a [processing
-instruction](#processing-instruction), an [element type
-declaration](#element-type-declaration), or a [CDATA
-section](#cdata-section).
-
-Here are some simple open tags:
-
-.
-
-.
-

-.
-
-Empty elements:
-
-.
-
-.
-

-.
-
-Whitespace is allowed:
-
-.
-
-.
-

-.
-
-With attributes:
-
-.
-
-.
-

-.
-
-Illegal tag names, not parsed as HTML:
-
-.
-<33> <__>
-.
-
<33> <__>

-.
-
-Illegal attribute names:
-
-.
-
-.
-
<a h*#ref="hi">

-.
-
-Illegal attribute values:
-
-.
-
-.
-
</a href="foo">

-.
-
-Comments:
-
-.
-foo 
-.
-
foo 

-.
-
-.
-foo 
-.
-
foo <!-- not a comment -- two hyphens -->

-.
-
-Processing instructions:
-
-.
-foo 
-.
-
foo 

-.
-
-Declarations:
-
-.
-foo 
-.
-
foo 

-.
-
-CDATA sections:
-
-.
-foo &<]]>
-.
-
foo &<]]>

-.
-
-Entities are preserved in HTML attributes:
-
-.
-
-.
-

-.
-
-Backslash escapes do not work in HTML attributes:
-
-.
-
-.
-

-.
-
-.
-
-.
-
<a href=""">

-.
-
-## Hard line breaks
-
-A line break (not in a code span or HTML tag) that is preceded
-by two or more spaces is parsed as a linebreak (rendered
-in HTML as a `
` tag):
-
-.
-foo  
-baz
-.
-
foo

-baz

-.
-
-For a more visible alternative, a backslash before the newline may be
-used instead of two spaces:
-
-.
-foo\
-baz
-.
-
foo

-baz

-.
-
-More than two spaces can be used:
-
-.
-foo       
-baz
-.
-
foo

-baz

-.
-
-Leading spaces at the beginning of the next line are ignored:
-
-.
-foo  
-     bar
-.
-
foo

-bar

-.
-
-.
-foo\
-     bar
-.
-
foo

-bar

-.
-
-Line breaks can occur inside emphasis, links, and other constructs
-that allow inline content:
-
-.
-*foo  
-bar*
-.
-
foo

-bar

-.
-
-.
-*foo\
-bar*
-.
-
foo

-bar

-.
-
-Line breaks do not occur inside code spans
-
-.
-`code  
-span`
-.
-
code span

-.
-
-.
-`code\
-span`
-.
-
code\ span

-.
-
-or HTML tags:
-
-.
-
-.
-

-.
-
-.
-
-.
-

-.
-
-## Soft line breaks
-
-A regular line break (not in a code span or HTML tag) that is not
-preceded by two or more spaces is parsed as a softbreak.  (A
-softbreak may be rendered in HTML either as a newline or as a space.
-The result will be the same in browsers. In the examples here, a
-newline will be used.)
-
-.
-foo
-baz
-.
-
foo
-baz

-.
-
-Spaces at the end of the line and beginning of the next line are
-removed:
-
-.
-foo 
- baz
-.
-
foo
-baz

-.
-
-A conforming parser may render a soft line break in HTML either as a
-line break or as a space.
-
-A renderer may also provide an option to render soft line breaks
-as hard line breaks.
-
-## Strings
-
-Any characters not given an interpretation by the above rules will
-be parsed as string content.
-
-.
-hello $.;'there
-.
-
hello $.;'there

-.
-
-.
-Foo χρῆν
-.
-
Foo χρῆν

-.
-
-Internal spaces are preserved verbatim:
-
-.
-Multiple     spaces
-.
-
Multiple     spaces

-.
-
-
-
-# Appendix A: A parsing strategy {-}
-
-## Overview {-}
-
-Parsing has two phases:
-
-1. In the first phase, lines of input are consumed and the block
-structure of the document---its division into paragraphs, block quotes,
-list items, and so on---is constructed.  Text is assigned to these
-blocks but not parsed. Link reference definitions are parsed and a
-map of links is constructed.
-
-2. In the second phase, the raw text contents of paragraphs and headers
-are parsed into sequences of Markdown inline elements (strings,
-code spans, links, emphasis, and so on), using the map of link
-references constructed in phase 1.
-
-## The document tree {-}
-
-At each point in processing, the document is represented as a tree of
-**blocks**.  The root of the tree is a `document` block.  The `document`
-may have any number of other blocks as **children**.  These children
-may, in turn, have other blocks as children.  The last child of a block
-is normally considered **open**, meaning that subsequent lines of input
-can alter its contents.  (Blocks that are not open are **closed**.)
-Here, for example, is a possible document tree, with the open blocks
-marked by arrows:
-
-``` tree
--> document
-  -> block_quote
-       paragraph
-         "Lorem ipsum dolor\nsit amet."
-    -> list (type=bullet tight=true bullet_char=-)
-         list_item
-           paragraph
-             "Qui *quodsi iracundia*"
-      -> list_item
-        -> paragraph
-             "aliquando id"
-```
-
-## How source lines alter the document tree {-}
-
-Each line that is processed has an effect on this tree.  The line is
-analyzed and, depending on its contents, the document may be altered
-in one or more of the following ways:
-
-1. One or more open blocks may be closed.
-2. One or more new blocks may be created as children of the
-   last open block.
-3. Text may be added to the last (deepest) open block remaining
-   on the tree.
-
-Once a line has been incorporated into the tree in this way,
-it can be discarded, so input can be read in a stream.
-
-We can see how this works by considering how the tree above is
-generated by four lines of Markdown:
-
-``` markdown
-> Lorem ipsum dolor
-sit amet.
-> - Qui *quodsi iracundia*
-> - aliquando id
-```
-
-At the outset, our document model is just
-
-``` tree
--> document
-```
-
-The first line of our text,
-
-``` markdown
-> Lorem ipsum dolor
-```
-
-causes a `block_quote` block to be created as a child of our
-open `document` block, and a `paragraph` block as a child of
-the `block_quote`.  Then the text is added to the last open
-block, the `paragraph`:
-
-``` tree
--> document
-  -> block_quote
-    -> paragraph
-         "Lorem ipsum dolor"
-```
-
-The next line,
-
-``` markdown
-sit amet.
-```
-
-is a "lazy continuation" of the open `paragraph`, so it gets added
-to the paragraph's text:
-
-``` tree
--> document
-  -> block_quote
-    -> paragraph
-         "Lorem ipsum dolor\nsit amet."
-```
-
-The third line,
-
-``` markdown
-> - Qui *quodsi iracundia*
-```
-
-causes the `paragraph` block to be closed, and a new `list` block
-opened as a child of the `block_quote`.  A `list_item` is also
-added as a child of the `list`, and a `paragraph` as a child of
-the `list_item`.  The text is then added to the new `paragraph`:
-
-``` tree
--> document
-  -> block_quote
-       paragraph
-         "Lorem ipsum dolor\nsit amet."
-    -> list (type=bullet tight=true bullet_char=-)
-      -> list_item
-        -> paragraph
-             "Qui *quodsi iracundia*"
-```
-
-The fourth line,
-
-``` markdown
-> - aliquando id
-```
-
-causes the `list_item` (and its child the `paragraph`) to be closed,
-and a new `list_item` opened up as child of the `list`.  A `paragraph`
-is added as a child of the new `list_item`, to contain the text.
-We thus obtain the final tree:
-
-``` tree
--> document
-  -> block_quote
-       paragraph
-         "Lorem ipsum dolor\nsit amet."
-    -> list (type=bullet tight=true bullet_char=-)
-         list_item
-           paragraph
-             "Qui *quodsi iracundia*"
-      -> list_item
-        -> paragraph
-             "aliquando id"
-```
-
-## From block structure to the final document {-}
-
-Once all of the input has been parsed, all open blocks are closed.
-
-We then "walk the tree," visiting every node, and parse raw
-string contents of paragraphs and headers as inlines.  At this
-point we have seen all the link reference definitions, so we can
-resolve reference links as we go.
-
-``` tree
-document
-  block_quote
-    paragraph
-      str "Lorem ipsum dolor"
-      softbreak
-      str "sit amet."
-    list (type=bullet tight=true bullet_char=-)
-      list_item
-        paragraph
-          str "Qui "
-          emph
-            str "quodsi iracundia"
-      list_item
-        paragraph
-          str "aliquando id"
-```
-
-Notice how the newline in the first paragraph has been parsed as
-a `softbreak`, and the asterisks in the first list item have become
-an `emph`.
-
-The document can be rendered as HTML, or in any other format, given
-an appropriate renderer.
-
-
diff --git a/test/data/packagedocs/stdlib.md b/test/data/packagedocs/stdlib.md
deleted file mode 100644
index 5d7432b5..00000000
--- a/test/data/packagedocs/stdlib.md
+++ /dev/null
@@ -1,11 +0,0 @@
-# Module stdlib
-
-## Kotlin Standard Library
-
-The Kotlin standard library is a set of functions and types implementing idiomatic patterns when working with collections,
-text and files.
-
-# Package kotlin
-
-Core functions and types
-
diff --git a/test/data/packages/dottedNamePackage.kt b/test/data/packages/dottedNamePackage.kt
deleted file mode 100644
index 38619310..00000000
--- a/test/data/packages/dottedNamePackage.kt
+++ /dev/null
@@ -1 +0,0 @@
-package dot.name
\ No newline at end of file
diff --git a/test/data/packages/rootPackage.kt b/test/data/packages/rootPackage.kt
deleted file mode 100644
index e69de29b..00000000
diff --git a/test/data/packages/simpleNamePackage.kt b/test/data/packages/simpleNamePackage.kt
deleted file mode 100644
index 2c29f4c7..00000000
--- a/test/data/packages/simpleNamePackage.kt
+++ /dev/null
@@ -1 +0,0 @@
-package simple
diff --git a/test/data/packages/simpleNamePackage2.kt b/test/data/packages/simpleNamePackage2.kt
deleted file mode 100644
index 2c29f4c7..00000000
--- a/test/data/packages/simpleNamePackage2.kt
+++ /dev/null
@@ -1 +0,0 @@
-package simple
diff --git a/test/data/properties/annotatedProperty.kt b/test/data/properties/annotatedProperty.kt
deleted file mode 100644
index 8990af29..00000000
--- a/test/data/properties/annotatedProperty.kt
+++ /dev/null
@@ -1 +0,0 @@
-@Volatile var property = "test"
\ No newline at end of file
diff --git a/test/data/properties/propertyOverride.kt b/test/data/properties/propertyOverride.kt
deleted file mode 100644
index 625d1da0..00000000
--- a/test/data/properties/propertyOverride.kt
+++ /dev/null
@@ -1,7 +0,0 @@
-open class Foo() {
-    open val xyzzy: Int get() = 0
-}
-
-class Bar(): Foo() {
-    override val xyzzy: Int get() = 1
-}
diff --git a/test/data/properties/propertyWithReceiver.kt b/test/data/properties/propertyWithReceiver.kt
deleted file mode 100644
index e282f6bd..00000000
--- a/test/data/properties/propertyWithReceiver.kt
+++ /dev/null
@@ -1,2 +0,0 @@
-val String.foobar: Int
-    get() = size() * 2
diff --git a/test/data/properties/valueProperty.kt b/test/data/properties/valueProperty.kt
deleted file mode 100644
index b87cce57..00000000
--- a/test/data/properties/valueProperty.kt
+++ /dev/null
@@ -1 +0,0 @@
-val property = "test"
\ No newline at end of file
diff --git a/test/data/properties/valuePropertyWithGetter.kt b/test/data/properties/valuePropertyWithGetter.kt
deleted file mode 100644
index 64d3848c..00000000
--- a/test/data/properties/valuePropertyWithGetter.kt
+++ /dev/null
@@ -1,2 +0,0 @@
-val property: String
-    get() = "test"
\ No newline at end of file
diff --git a/test/data/properties/variableProperty.kt b/test/data/properties/variableProperty.kt
deleted file mode 100644
index 54ab4595..00000000
--- a/test/data/properties/variableProperty.kt
+++ /dev/null
@@ -1 +0,0 @@
-var property = "test"
\ No newline at end of file
diff --git a/test/data/properties/variablePropertyWithAccessors.kt b/test/data/properties/variablePropertyWithAccessors.kt
deleted file mode 100644
index 152fb7d0..00000000
--- a/test/data/properties/variablePropertyWithAccessors.kt
+++ /dev/null
@@ -1,4 +0,0 @@
-var property: String
-    get() = "test"
-    set(value) {
-    }
\ No newline at end of file
-- 
cgit