Cppfront : A new syntax for C++ (page 4)

On 19.09.22 20:41, Walter Bright wrote: > On 9/19/2022 2:30 AM, Dukc wrote: >> I think you mean memory safe RAII and reference counting. DIP1000 enables limited forms of those, but in practice one still tends to be stuck mostly with the GC, static memory and the stack. > > @live, which deals with memory allocation, is the step after DIP1000. > (It's a linting tool and it does nothing to enhance @safe safety guarantees because it is a function attribute.)

September 25, 2022

Re: Cppfront : A new syntax for C++

Posted by German Diago
in reply to IGotD-

Permalink

German Diago

Posted in reply to IGotD-

Permalink

On Saturday, 17 September 2022 at 15:56:54 UTC, IGotD- wrote:

On Saturday, 17 September 2022 at 11:08:37 UTC, Tejas wrote:

https://github.com/hsutter/cppfront

People working towards syntax improvements as well to C++ now, which they believe will pave the way for semantic improvements that break backwards compatibility with C++

When C++ compile times aren't long enough, let's make them longer.

This is the wrong judgement to do (about compile times). Compile times with modules are shorter. Cpp2 pushes for modules, not for include, but pure modules.

Besides that, there are things such as tuples (multiple return values) done without templates, which avoids instantiation.

Also, take into account that cppfront being a preprocessor is an implementation detail to easily be able to mix and match cpp/cpp2 and that some day it could become a full-fledged compiler. Cpp2 is thought for transition to pure cpp2 but 100% compatible. This means that preprocessing by lowering is a technique, but not the only technique.

Greetings.

Forums