# \#guidelines **URL:** https://discourse.bemanproject.org/tag/guidelines/3.md [Latest](https://discourse.bemanproject.org/latest.md) · [Categories](https://discourse.bemanproject.org/categories.md) · [Tags](https://discourse.bemanproject.org/tags.md) --- ## [Benchmark Infrastructure](https://discourse.bemanproject.org/t/benchmark-infrastructure/598)
**Author:** [@arthur](https://discourse.bemanproject.org/u/arthur)\ **Replies:** 2\ **Last updated:** [August 8, 2026, 4:36pm UTC](https://discourse.bemanproject.org/t/benchmark-infrastructure/598 "2026-08-08T16:36:15Z")
Similar to the Test infrastructure thread, I’d like to field recommendations for benchmarking libraries and requirements we hold over them. To the latter point, if I understand correctly, portability and easy vendoring … --- ## [Test Infrastructure: preferably not Google Test!](https://discourse.bemanproject.org/t/test-infrastructure-preferably-not-google-test/150)
**Author:** [@dietmarkuehl](https://discourse.bemanproject.org/u/dietmarkuehl)\ **Replies:** 30\ **Last updated:** [August 1, 2026, 5:59pm UTC](https://discourse.bemanproject.org/t/test-infrastructure-preferably-not-google-test/150 "2026-08-01T17:59:07Z")
Introduction We recently discussed how tests of Beman projects should be implemented. There was a post (by Louis Dionne) somewhere I can’t find arguing that tests based on assert() potentially allow their use by standard… --- ## [Potential Policy Change: Making C++20 the minimum library implementation](https://discourse.bemanproject.org/t/potential-policy-change-making-c-20-the-minimum-library-implementation/581)
**Author:** [@Jeff-Garland](https://discourse.bemanproject.org/u/Jeff-Garland)\ **Replies:** 9\ **Last updated:** [June 1, 2026, 3:59pm UTC](https://discourse.bemanproject.org/t/potential-policy-change-making-c-20-the-minimum-library-implementation/581 "2026-06-01T15:59:00Z")
During the review of indirect today the horror of all the c++17 ifdef’s to make up for the lack of concepts was everywhere. Given that new Beman libraries should be targeting c++29 and beyond, many people thought that … --- ## [Target\_compile\_features must not used?](https://discourse.bemanproject.org/t/target-compile-features-must-not-used/554)
**Author:** [@ClausKlein](https://discourse.bemanproject.org/u/ClausKlein)\ **Replies:** 2\ **Last updated:** [January 18, 2026, 6:27pm UTC](https://discourse.bemanproject.org/t/target-compile-features-must-not-used/554 "2026-01-18T18:27:06Z")
from beman\_standard \[cmake.passive\_targets\] Requirement: External targets must not modify compilation flags of dependents. Therefore, target\_compile\_features (e.g., cxx\_std\_20) must not be used because it modifies the… --- ## [Make project layout evoke-compatible?](https://discourse.bemanproject.org/t/make-project-layout-evoke-compatible/457)
**Author:** [@dascandy](https://discourse.bemanproject.org/u/dascandy)\ **Replies:** 8\ **Last updated:** [October 4, 2025, 4:06pm UTC](https://discourse.bemanproject.org/t/make-project-layout-evoke-compatible/457 "2025-10-04T16:06:16Z")
The goal behind Evoke is to rely solely on the code itself, and the directory structure around the code, to determine what makes up which components, and which components are which type. The Beman project setup is almos… --- ## [New Beman Standard CMake Recommendations: Implicit Defaults and (No) Single-Use Variables](https://discourse.bemanproject.org/t/new-beman-standard-cmake-recommendations-implicit-defaults-and-no-single-use-variables/429)
**Author:** [@vito.gamberini](https://discourse.bemanproject.org/u/vito.gamberini)\ **Replies:** 7\ **Last updated:** [June 2, 2025, 3:53pm UTC](https://discourse.bemanproject.org/t/new-beman-standard-cmake-recommendations-implicit-defaults-and-no-single-use-variables/429 "2025-06-02T15:53:17Z")
The Beman Standard CMake requirements and recommendations are in good shape, I would like to propose adding two more recommendations to guide the existing projects as we prepare them for packaging. Proposal \[CMAKE.IMPLI… --- ## [Maintain both versions of a library - latest released standard, and the one under development (e.g. now it will be C++23, C++26)](https://discourse.bemanproject.org/t/maintain-both-versions-of-a-library-latest-released-standard-and-the-one-under-development-e-g-now-it-will-be-c-23-c-26/307)
**Author:** [@InbalL](https://discourse.bemanproject.org/u/InbalL)\ **Replies:** 5\ **Last updated:** [January 24, 2025, 3:25pm UTC](https://discourse.bemanproject.org/t/maintain-both-versions-of-a-library-latest-released-standard-and-the-one-under-development-e-g-now-it-will-be-c-23-c-26/307 "2025-01-24T15:25:00Z")
To followup on the meeting - I would like to start a discussion on having two different visions of same library. I would like to advocate for keeping two versions of the same library (only in case the two versions are di… --- ## [Contribution opportunities](https://discourse.bemanproject.org/t/contribution-opportunities/161)
**Author:** [@hels15](https://discourse.bemanproject.org/u/hels15)\ **Replies:** 3\ **Last updated:** [August 1, 2024, 2:22pm UTC](https://discourse.bemanproject.org/t/contribution-opportunities/161 "2024-08-01T14:22:01Z")
I’m looking forward to contributing to any currently available projects. I reckoned, the ones that were mentioned here before are already implemented. Could someone help me figure out how I can find projects to contrib… --- ## [Beman Project coding guidelines](https://discourse.bemanproject.org/t/beman-project-coding-guidelines/88)
**Author:** [@dietmarkuehl](https://discourse.bemanproject.org/u/dietmarkuehl)\ **Replies:** 16\ **Last updated:** [May 20, 2024, 4:01pm UTC](https://discourse.bemanproject.org/t/beman-project-coding-guidelines/88 "2024-05-20T16:01:31Z")
I’m ready to contribute. So far, there isn’t much there to follow. It seems prudent to code according to an agreed set of guidelines to make the code reasonably consistent. Code layout (indentation, placement of curlies/…