Welcome to cppfront Discussions!

[hsutter]

Opening note, 11 Aug 2023:
In late 2022, I first opened this repo without Issues or Discussions enabled. I quickly found that issues were being submitted anyway... as PRs. So, in response to demand, I opened Issues. (Insert the "wait for the campus' users to walk ruts into the field to show you where to put the paths" reference here.) I appreciate all your bug and quality-of-implementation reports that have come in there. Thanks!
Now I've started seeing Q&A discussions happening anyway... in Issues. So, again in response to demand including requests like #577, I'm opening up Discussions. I'll go ahead and take a pass through the existing issues to convert them to discussions where that seems appropriate.
— Herb

👋 Welcome!

Discussions is a place to:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others, be open-minded, and be kind.

Note the Code of Conduct always applies. In a nutshell, because it's worth repeating: Always be kind. Thank you!

[lemanschik]

do not worry since you opened the repo a lot did change. while most people have rudimentary cpp2 front ends today i expect that we soon will be able to use something like "Gorilla ML" to Implement LLVM Language Frontends. then we do not even need normal maintainers anymore as LLVM offers a Solid API and Grolla ML can use that API with 90+ % there is enough space for exploration soon.

My most best cpp2 frontend is at present generated for GraalVM using the Truffle API and Gorilla. But i am improving the usability at present. I have chosen GraalVM because there exists LLVM support and i can use still use the JVM and GraalVM Debugging tools like Ast Visualizers and that.

My new Final goal is now to get a LLVM only cpp2 frontend AI generated and Compiled via cpp2 on graalvm which got again Implemented by AI.

my real goal is not to implement cpp2 but my goal is to implement any Language Faster and integrate it with existing tooling. For example the GraalVM cpp2 supports the vscode GraalVM extension and debugging tools so i can even use chrome devtools for cpp2 debugging even cross language boundaray.

I Only wanted to update you here as you updated us.

Much love for you.

[Gangneron]

@hsutter
Hello sorry by advanced if this is not the place to ask my first question but I am new and I want to know if the project aims to replace c++ or if it is a test branch for after improved c++ by proposing these modifications to ISO c++. I also want to know how I can help you. I have an intermediate level in programming but I don't understand all the concepts of C++. But I can come up with ideas and write code and documentation.
Thanks in advance

[gregmarr]

A good place to start to learn about the project is to read the README and then watch the 2022 and 2023 CppCon talks.

@hsutter The 2023 talk isn't linked from the README. That would be good to add.

[hsutter]

@Gangneron Thanks for the interest! It's currently a place for me to try out my own C++ evolution proposals for C++, and yes I plan to continue to propose specific features and potentially the entire alternative syntax as a proposal for ISO C++.

@gregmarr Oh, right -- thanks for the reminder. Done: 7570f4f

[Gangneron]

Ok i create a new suggestion for secure memory totomorrow. But during the ISO C++ conference would I have the right to propose the same ideas or should I keep them for this project? Le jeu. 4 janv. 2024 à 21:38, gregmarr ***@***.***> a écrit :

…

A good place to start to learn about the project is to read the README <https://github.com/hsutter/cppfront/blob/main/README.md> and then watch the 2022 and 2023 CppCon talks. @hsutter <https://github.com/hsutter> The 2023 talk isn't linked from the README. That would be good to add. — Reply to this email directly, view it on GitHub <#580 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAMPRSAABRRPW5AFRH57XN3YM4HMXAVCNFSM6AAAAAA3NSWGCKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DAMJWHE2DM> . You are receiving this because you commented.Message ID: ***@***.***>

[JohelEGP]

Oh, so you're looking to use cppfront to implement a Cpp1 proposal?
P2971 did that, although the implementation wasn't floated around in this repository.

[Gangneron]

if this poses a problem I don't do it but I think it could be interesting Le jeu. 4 janv. 2024 à 22:22, Johel Ernesto Guerrero Peña < ***@***.***> a écrit :

…

Oh, so you're looking to use cppfront to implement a Cpp1 proposal? P2971 <https://wg21.link/P2971> did that, although the implementation wasn't floated around in this repository. — Reply to this email directly, view it on GitHub <#580 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAMPRSBDTZ3CAQCX6AYEDUTYM4MR5AVCNFSM6AAAAAA3NSWGCKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DAMJXGM2DI> . You are receiving this because you commented.Message ID: ***@***.***>

[Gangneron]

I will finish making the proposal over the weekend because I still have the translation to do

[akornilov]

Hello!

I am newbie in cppfront and have a question.
I don't understand how to separate declaration and definition of functions and classes.
What is right way to separate code to *.h2 and *.cpp2 files?
How to compile such files via cppfornt tool?
Are there documentation about this case?

[akornilov]

Does cppfront support C++20 modules?

[JohelEGP]

Does it works for classes?

Sure.

Does cppfront support C++20 modules?

It has some support for import std;. See https://hsutter.github.io/cppfront/cppfront/options/#-import-std-im.

[akornilov]

I mean own module. Is it possible to create module with arbitrary exports using cpp2 syntax and imports this module in the other place?

[JohelEGP]

No, it's not part of the Cpp2 grammar.

[akornilov]

Usually project are separated into several libraries. Are any way to do this in cppfront?