Talking about and documenting multiple groups is strange

[epage]

Without an item in the documentation for this, it makes it hard to talk about and document

[epage]

I would name this Message.

A requirement for me is that fn renders signature references the item.

I think a typdef could work for that.

Or we could have a pub struct Message<'g>(pub &'g [Group]) with a From<&[Group]>

[epage]

Turns out we have Message for Title-like inside of a Group.

We could call the top-level type

• Message (preferred)
• Report (preferred)
• Diagnostic
  • I worry Diagnostic might make people think this is a high level diagnostic type that they should pass around
• Document

We could call Message,

• Message (preferred)
• Content (preferred)
  • Feels like its a general paragraph, not one that will have a label.
• Body
  • Feels like its a general paragraph, not one that will have a label.
• Line
  • Feels like its a general paragraph, not one that will have a label.
• Stanza
• Subject
  • Confusable with Title?

Prior art:

• codespan_reporting calls the top-level a Diagnostic.
• ariadne calls it a Report