html5tokenizer/tests, branch v0.5.0

feat: introduce NaiveParser

2023-08-19T11:53:58Z

break!: remove DefaultEmitter from public API

2023-08-19T11:41:55Z

docs: link multipage version of HTML spec

2023-08-19T11:41:55Z

chore: switch from pretty_assertions to similar-asserts

2023-08-19T11:41:55Z

In the next commit I'm adding a test that compares the content of files and pretty_assertions doesn't omit large portions of unchanged lines in its diff[1] (contrary to similar-asserts). (Sidenote: We already depend on similar via insta.) [1]: https://github.com/rust-pretty-assertions/rust-pretty-assertions/issues/114

break!: stop abusing Display for Error codes

2023-08-19T11:41:55Z

Display impls should return human-readable strings. After this commit we're able to introduce a proper Display impl in the future without that being a breaking change.

feat!: add span and offsets to Doctype

2023-08-19T11:41:55Z

fix: report value offset/span as None for the empty attr syntax

2023-08-19T11:41:55Z

break!: introduce AttributeMap

2023-08-19T11:41:55Z

This has a number of benefits: * it hides the implementation of the map * it hides the type used for the map values (which lets us e.g. change name_span to name_offset while still being able to provide a convenient `Attribute::name_span` method.) * it lets us provide convenience impls for the map such as `FromIterator<(String, String)>`

feat!: add all-inclusive spans to tags

2023-08-19T11:41:55Z

Also more performant since we no longer have to update the name span on every Emitter::push_tag_name call.

fix: fix lots of position off-by-ones

2023-08-19T11:41:55Z

Previously the PosTrackingReader always mysteriously subtracted 1 from the current position ... this wasn't sound at all ... the machine just happens to often call `Tokenizer::unread_char` ... but not always. E.g. for proper comments it didn't which resulted in their offset and spans being off-by-one, which is fixed by this commit (see test_spans.rs).