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

Additional test scenario required here #1564

Open
SergeyKopienko opened this issue May 6, 2024 · 3 comments
Open

Additional test scenario required here #1564

SergeyKopienko opened this issue May 6, 2024 · 3 comments
Assignees

Comments

@SergeyKopienko
Copy link
Contributor

SergeyKopienko commented May 6, 2024

#include "support/test_config.h"

Additional test scenario required here:

  • when #include "support/test_config.h" is the first include;
  • when #include "support/test_config.h" is the last include;
  • for all header_inclusion_*.pass.cpp files.
@SergeyKopienko
Copy link
Contributor Author

Probably after merge the PR #1250 this issue isn't actual.
@danhoeflinger, @kboyarinov how do you thinks?

@SergeyKopienko SergeyKopienko self-assigned this Sep 20, 2024
@kboyarinov
Copy link
Contributor

I am not aware (or not remember:)) on what initially caused this issue and why the additional testing was required. If you remind me, I would be able to advice if the issue was fixed by my PR or not.

@danhoeflinger
Copy link
Contributor

This issue was added when we added #include <version> (or its predecessor) in to test_config.h (which was merged after #1250) from this comment: #1548 (review).

Currently, all of these header inclusion tests include test/support/test_config.h first, which in turn includes <version> or <ciso646>. The intention here was to have a test of the alternative to check for include order issues in combination with STL.

I'm not sure if these tests would show the issue #1250 fixes, but it being fixed doesn't remove the want for a test. #1584 extends the fixes for #1250 further, so there are probably multiple cases here that could deserve testing for regression if we don't have them already.

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

No branches or pull requests

3 participants