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

Towards making candidate libraries testable in Compiler Explorer #130

Open
akrzemi1 opened this issue Aug 14, 2023 · 3 comments
Open

Towards making candidate libraries testable in Compiler Explorer #130

akrzemi1 opened this issue Aug 14, 2023 · 3 comments

Comments

@akrzemi1
Copy link
Member

This is more like an idea, as I do not have a concrete recipe for the moment.
The ultimate goal would be to have libraries that are candidates for inclusion into Boost, especially during the review period, to be testable in an online environment, such as Compiler Explorer.
This would enable the feedback from people who do not have time or capabilities to install a candidate library in their environments.
Potential reviewers are volunteers, have their private lives and they $dayjobs, and the review period is relatively short. They are often put off by the time it is required to perform a review. Writing the report is time consuming itself. Environment setup is an additional unnecessary effort.
Of course, library authors are also volunteers with similar constraints, so burdening them with the additional requirement is also not a good option.
But maybe Boost website could offer an instruction or scripts for making the online access to the testing environment easier. Maybe a hot line channel with Matt Godbolt? Something that would make it easy for library authors to install their library in the testing environment. Or something for the reviewers to do so. Or a server similar in spirit to Compiler Explorer where the candidate libraries can be tested. This would be useful not only during reviews. Official Boost libraries would also benefit from such online demos. This would help developers decide if they want to use Boost.

@vinniefalco
Copy link
Member

At a minimum, the documentation could include a sentence or paragraph explaining how making a header-only version of the library purely for review (if the library is not already strictly header-only) is a help for compiler explorer.

@akrzemi1
Copy link
Member Author

It could offer a script that, for header-only libraries, iterates over the include/boost folder and produces one big flat header with all the contents. This will not work for compiled libraries, but is still something.

@grafikrobot
Copy link
Member

Compiler explorer now has a way to "Load from ZIP" a whole IDE style project. If someone could figure out how to make ZIPs that work with that and post a guide for lib authors, they could provide a CE compatible ZIP as part of the review.

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