Skip to content

fix: Force group levels to be explicitly given #237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 1, 2025

Conversation

epage
Copy link
Contributor

@epage epage commented Jul 1, 2025

Moved from Group::new().primary_level(level) to
Group::with_level(level).

As a convenience for titled-groups, we have Group::with_title(title).

I had considered child/children methods on Title to make a group but that didn't work out well for title-only groups and I feel like this design is more consistent / easier to discover.

Moved from `Group::new().primary_level(level)` to
`Group::with_level(level)`.

As a convenience for titled-groups, we have `Group::with_title(title)`.

I had considered `child`/`children` methods on `Title` to make a group
but that didn't work out well for title-only groups and I feel like this
design is more consistent / easier to discover.
@epage epage force-pushed the group-title branch 3 times, most recently from 28f5279 to 49322a7 Compare July 1, 2025 21:35
@Muscraft Muscraft merged commit 5218ce0 into rust-lang:master Jul 1, 2025
15 checks passed
@epage epage deleted the group-title branch July 1, 2025 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants