There is a lot of content out there that uses this behavior. Actually, HTML5 mandates that

<p>1<p>2<h1>head1</h1>

and

<p>1</p><p>2</p><h1>head1</h1>

MUST be treated equally. Sadly, some HTML edit components emit such stuff.

At present the parser looses this content:

/*	
See: http://www.w3.org/TR/html50/grouping-content.html#the-p-element

A p element's

README is kind of out of date as some description still in Swift 3.

• English
• Chinese
• Japanese

This would give us a better starting point for getting a Kubernetes cluster up and running in the future.
Maybe also using the GraalVM with native binaries. As we didn't use reflection and other stuff which would prohibit the use of native binaries the only thing now is that we moved to Java 13 and the GraalVM just started to support Java 11.

I learned from the API documentation that the SelectorList class contains a remove method. But I don't see it in v1.5.2.

XQuery Write Locks should be restricted to updating expressions. We could…

1. raise an exception if such an annotation is defined, and if the code is non-updating, or
2. ignore locks that do not match the category (read-only, updating) of the expression to be run.

Option 2 may be the more flexible one, as it still allows users to defin

Is your feature request related to a problem? Please describe.

Running the code below will result in two different error messages:

xquery version "3.1";

try { [1,2,3,4](-1) } catch err:FOAY0001 { $err:description },
try { array:get([1,2,3,4], -1) } catch err:FOAY0001 { $err:description }

• "Array index out of bounds. Position -1 does not exist in this array. Length

Reported by @davidsulc

Currently, the Meeseeks.Parser module is private (@moduledoc false) which means that it's not possible for users to determine the proper parameters to (e.g.) Meeseeks.parse/2 by looking at the docs (as they refer to an undocumented module)