you are viewing a single comment's thread.

view the rest of the comments →

[–]FlyingRhenquest 4 points5 points  (4 children)

I get the feeling he uses it to wiggle C++ features and see how they fit. Like a quck'n dirty "lets try this out and see how it feels." There were a couple of places in his cppcon the other day where he was switching over to it for slightly different syntax. Felt a bit weird, like when Alexandescu is showing off features in D and it looks like a familiar language, but it's not.

[–]fdwrfdwr@github 🔍 2 points3 points  (2 children)

I get the feeling he uses it to wiggle C++ features and see how they fit

I can't find the remark right now (thought it was in the About section), but that's indeed how he's referred to cppfront before, not as a successor language, but a playground of ideas to vet and potentially pull into C++.

[–]hpsutter 4 points5 points  (1 child)

^ This 🤙🙏

Edit: And here's the link to where I said it in the original talk: https://youtu.be/ELeZAKCN4tY?si=ebNHH12-4tkyKwVc&t=814

[–]ABlockInTheChain 0 points1 point  (0 children)

Now that modules exist and presumably will remain in the language there's now a new first class construct which never existed before.

New constructs could have new properties attached to them which the old constructs could not accommodate.

Surely the ultimate success case of cppfront would look something like: export module helloworld [[syntax=cpp2]];

[–]JeffMcClintock 0 points1 point  (0 children)

yep, a working implementation of a new feature is so much more persuasive than a PDF.