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

maint: Remove anonymous namespace in tests #3664

Closed

Conversation

mathbunnyru
Copy link
Contributor

No description provided.

}

using namespace mamba::specs::match_spec_literals;
using Request = solver::Request;

namespace
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I added this one because mpkg function is also present in another test file (and I added anon namespace there as well)

}
} // namespace mamba
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This comment seems to be wrong, I think it was 2 nested anonymous namespaces

@jjerphan
Copy link
Member

Naive question: can you explain what is the plus-value of those changes whose diff is large an noisy?

@mathbunnyru
Copy link
Contributor Author

Naive question: can you explain what is the plus-value of those changes whose diff is large an noisy?

Well, not much, but it makes tests look more consistent (and a bit shorter).
I'm completely OK closing this PR.

I told I would work on this when I was working on Catch2, so delivering my promise: #3618 (comment)

@jjerphan jjerphan added the release::bug_fixes For PRs fixing bugs label Dec 11, 2024
@JohanMabille
Copy link
Member

In that case I would find it safer to replace anonymous namespaces with named namespaces instead of removing them. This could lead to duplicated symbols in the future because of tests with very gneric names (constructor, swap, etc).

Keeping anonymous namespaces is fine too.

@jjerphan
Copy link
Member

I would also keep the anonymous namespace (and thus close this PR).

We could name them, but I would not act unless we see a real benefit or unless it fixes problems.

@mathbunnyru
Copy link
Contributor Author

Ok, closing this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release::bug_fixes For PRs fixing bugs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants