Skip to content
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

Refactoring graphviz_test for review #375

Merged
merged 3 commits into from
May 9, 2024

Conversation

sehe
Copy link
Contributor

@sehe sehe commented May 3, 2024

(note this PR builds on #374)

The code was mostly fine (except for unhygienic using namespace in
places), but it was hard to see what was covered.

I've seperated fixtures (sample input + expected output), and models into separate namespaces.

This simplifies invocations of the ComparisonDriver (test_graph).

Works around invalidation of bundle property maps (see boostorg#373).

The `#if SEHE_UNSTABLE_PROPERTY_MAPS_FIXED` section is there to signal
my intent to investigate a generalized fix under that issue. It doubles
as literate documentation of the need for the workaround, so it's less
likely to bite the unwary.
sehe added 2 commits May 8, 2024 14:39
The code was mostly fine (except for unhygienic `using namespace` in
places), but it was hard to see what was covered.

I've seperated fixtures (sample input + expected output) and this will
simplify invoking the ComparisonDriver (test_graph).
@sehe
Copy link
Contributor Author

sehe commented May 8, 2024

Updated for review comments #364 (comment)

Comment on lines +30 to +31
typedef std::map< node_t, Mass > expected_masses_t;
typedef std::map< edge_t, Weight > expected_weights_t;
Copy link
Contributor

Choose a reason for hiding this comment

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

Personally, I think the type names should be more like node_mass_map_t, edge_weight_map_t and the variables should be named expected_mass, etc, but I'm not going to hold up the review over it. :)

@jeremy-murphy jeremy-murphy merged commit 17acf25 into boostorg:develop May 9, 2024
7 checks passed
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