sct4sp / cest Goto Github PK

Hello Paul,

I would like to discuss formatting rules to make sure there is no ambiguity for future contributions. I use to clang-format everything and call it a day as it is clean, consistent, and easy to follow. I just wanted to know how you approach that matter to make sure I don't step on your boundaries.

Regards,
Jules

Not urgent, but this will be needed in the future to ensure tests don't take too long to compile and run

Hello Paul,

GCC 12.1 released with some very welcome updates, including the following

std::vector, std::basic_string, std::optional, and std::variant can be used in constexpr functions.

Full change list: https://gcc.gnu.org/gcc-12/changes.html

It might be worth replacing Cest's implementation of these containers with alias types (and maybe add those that aren't available in Cest ?). So far, replacing cest::vector with std::vector in my Brainfuck meta-compiler didn't break anything.

constexpr std::unique_ptr was also implemented as an experimental C++23, although I didn't test it yet:

std::unique_ptr can be used in constexpr functions.

So cest::unique_ptr might be subject for this change too at some point (if not already).

As a side note, this change isn't directly related to Cest but might be worth checking out:

New command-line option -fimplicit-constexpr can be used to make inline functions implicitly constexpr

Regards,
Jules

Currently make test only works from within the tests subdirectory.