The 1.8.0 release initially failed because of javadoc errors, most of which are fixed now. To make sure we spot these earlier next time, we should enable doclint and javadoc production in CI

Example formatter output of reduced test case:

task t;
  a_pkg::foo #(x)::func();
endtask

Should be:

task t;
  a_pkg::foo#(x)::func();
endtask

Documentation for options for parse error handling and recovery are nonexistent. When a parse error occurs, what happens? What options are available for handling this error? How can I provide custom behavior for the exception that is raised when a parse error occurs?

Among others, Angular and Polymer allow you to define custom elements.
This is not supported with lesscpy

example code:

customtag .values {
    list-style: none;
}

More info:

• Angular: https://docs.angularjs.org/guide/directive
• Polymer custom elements: https://customelements.io/

Flex has a directive %option caseless to lex tokens in a case insensitive way.

Is there currently a way (besides using regular expressions) to accomplish the same?

厉害哦