cf.
#83

this makes the computation more wasteful but avoids issue 92. intermediate
results could end up in the memoization table and be treated as final by
later calls to h_follow(). this problem could appear or not depending on the
order of nonterminals (i.e. pointers) in a hashtable.

hammer/hammer#92

Resolve "assertion failure with ambiguous LALR compiles"

Closes #91

See merge request !34

Jni update

See merge request !36

print arena stats only when running test_suite --verbose

See merge request !33

development

update started from.

fixes issue 91

"assertion failure with ambiguous LALR compiles"
#91

i was trying to find out why the test suite suddenly insisted on being so
noisy. turns out glib now does TAP by default and all messages get printed,
--verbose or not. the old mode is considered deprecated.

cf.
https://en.wikipedia.org/wiki/Test_Anything_Protocol
https://gitlab.gnome.org/GNOME/glib/commit/ad175766575b23be920f41cdb1c350447c743347
https://gitlab.gnome.org/GNOME/glib/commit/19aafc4ca4dba2b63d24f01d23890ff30ef9b133

Token tweaks

See merge request !31

avoid a segfault when h_act_flatten() is called on a null token

See merge request !29

differantiate error codes from h_compile() and update documentation

See merge request !28

remove -Wno-clobbered from CFLAGS

See merge request !27

this omission has nagged me a number of times and i think it must have been a
simple oversight.

this way the assert will fire from the user's code rather than the one in
glue.c:h_seq_index() which is not informative without a stack trace.

also includes commented-out tests for functionality that i discovered we never
provided, namely position and length information at the granularity of
HParsedTokens. at the moment, these fields always seem to be 0. we should
probably fix that or get rid of them. in the latter case it might make sense
to move this information to HParseResult, so the user can get access to it via
h_action() as needed.

the regex backend already returned 2 for an internal failure, contrary to
documentation, so this mainly brings the latter in line with existing behavior.

at the same time, fix a bug: h_compile would previously return "false" (0) on
exceptions (longjmp).

make use of our new freedom to signal different error conditions from the
context-free backends, notably "incompatible combinator" vs. "unresolvable
conflict".

it breaks the build with clang.

Fix pointer signedness warning in h_literal()

See merge request !26

Unroll djbhash for ~25% speedup

See merge request !24

Hammer arena malloc speedup

See merge request !23

Hammer speedup

See merge request !22