Skip to content

Use pattern as domain separator #63

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

Draft
wants to merge 16 commits into
base: main
Choose a base branch
from

Conversation

recmo
Copy link
Contributor

@recmo recmo commented Jun 17, 2025

Builds on #62 and makes minimal diff replacement of DomainSeparator. Some of the functionality pattern provides is not used but will be used in an refactored/extended API. It's also awkwardly explicit in creating the patterns for testing, this will be fixed in a follow up refactoring PR.

Work in progress tests are not yet adapted.

Hierarchy::Begin => stack.push((position, interaction)),
Hierarchy::End => {
let Some((position, begin)) = stack.pop() else {
dbg!();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
dbg!();

label: Label,
/// The Rust name of the type of the value.
///
/// We use [`core::any::type_name`] to verify value types intead of [`core::any::TypeID`] since
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/// We use [`core::any::type_name`] to verify value types intead of [`core::any::TypeID`] since
/// We use [`core::any::type_name`] to verify value types instead of [`core::any::TypeID`] since

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