Robin Krahl

Thanks for the explanations! I’ll have a closer look at the text rendering code. > Can you describe the kind of things you want to do differently? It’s not about...

> I had a thought. Perhaps a useful extension point would be the point > where a sub-builder is merged into the parent. I like the idea! Maybe this could...

Another aspect to this topic is that it would be useful to use html2text’s layout mechanisms with a different data source, for example a Markdown document parsed with `pulldown-cmark` instead...

Also, I forgot to mention: As Rust doc comments mostly contain Rust code snippets, I just use the Rust syntax for syntax highlighting. But in general, HTML classes are used...

Alternatively, there could be a `StyledView` that wraps an arbitrary view and applies a style to the printer before drawing it, maybe together with a `Styleable` trait.

Could you add a macro that asserts that an enum variant exists?

Yes, that is mostly what I had in mind. In my case, I’m working with tuples of a string and a style annotation, namely [`genpdf::style::StyledString`](https://docs.rs/genpdf/0.2.0/genpdf/style/struct.StyledString.html) or [`genpdf::style::StyledStr`](https://docs.rs/genpdf/0.2.0/genpdf/style/struct.StyledStr.html). A paragraph is...

Thanks for the update! > One thought: would it make sense to combine `Splittable` with > `Fragment` and thus say that any type which a `Fragment` should have a >...

> * `SplittableFragment`: an abstract piece of text from which you can get a sub-fragment (your `Splittable` trait) > > * `MeasuredFragment`: an abstract piece of text which known how...

Yes, using a separate parser for the `reuse spdx` output would also be a way to implement this. Does this mean you’d rather not have this feature in reuse-tool directly?