cppfront
cppfront copied to clipboard
hsutter
A personal experimental C++ Syntax 2 -> Syntax 1 compiler
**Describe the bug** Clang produces a `Wshorten-64-to-32` warning with a `cpp2::range` when it is initialised with an integer literal as the first member and an expression producing a `size_t`/`size_type` as...
In the current implementation of cppfront (065a993), the following code compiles and runs: ```cpp i : int = 123; std::cout
The current implementation of `as()` for `std::any`, `std::optional`, and `std::variant` throws exceptions in case of tunability to cast. This behavior is inconsistent with runtime checked `as()` for signed/unsigned integral cast...
Steps to reproduce: - Get latest `cppfront` source code. - Compile `cppfront`, `g++ -std=c++20 cppfront.cpp`. - Run `cppfront` on this test file: ```cpp align_:=using"g"_: ``` Expected result: - Compilation success,...
The current implementation of `is_narrowing_v` does not handle type conversions correctly. For example, `cpp2::impl::is_narrowing_v` returns `false`, indicating that it mistakenly perceives the conversion from a signed `int` to an unsigned...
**Describe the bug** Assertion failure inside `find_definite_last_uses` in `sema.h` cppfront compiler when using boost::async and then continuations, not sure why exactly (could be order of evaluation when translating code? Just...
I.E. ``` numbers: std::array = ( 1, 2 ); ``` This idea was inspired by a comment made by Herb Sutter https://github.com/hsutter/cppfront/issues/1132#issuecomment-2184115637 Thoughts?
I am not aware of any way to hint the branch predictor in the new syntax I'd like to be able to use attributes, example cpp1 code: ``` if(condition) [[likely]]...
