Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Soursop and Ponies in Kona: A C++ Committee Trip Report

cor3ntin.github.io

Post reply on HN
Print view View original

11–20 of 69 posts

Re: Soursop and Ponies in Kona: A C++ Committee Trip Report

#11

Post by mkoubaa »

jvanderbot wrote: post #3

I would love to see a world in which a system is designed and built from multiple languages, so that the "right" tool could be used for each part. Does this even make sense? The modern distributed web seems to be leading us there. Slowly, slowly. I would also love to see a world where all C, C++ dependencies magically port themselves to Rust without FFI or a first-cut rewrite that a hobbyist did. 10-20 years maybe? U…

I've been dreaming about idiomatic interop for a while but by definition it's out of scope for any given language

Re: Soursop and Ponies in Kona: A C++ Committee Trip Report

#12

Post by cosmic_quanta »

saboot wrote: post #7

Still hoping for compile time introspection/reflection for class serialization. Whichever language implements it first (C++ or other) I'm all in on. I come from a scientific background, where running code on data gathering machines, and writing it out, then reading it back in later for analysis is 90% of what I do.

You can do this with Haskell (aeson package) and maybe with Rust (serde?)

Re: Soursop and Ponies in Kona: A C++ Committee Trip Report

#13

Post by Iamreadingthehn »

varajelle wrote: post #8
ape4 wrote: post #5

Herb's CppFront looks like the best hope for a clean C++ future

CppFront is a different project entirely. It's like saying C++ is C's future

CppFront compiles to C++ and everything is intended to map to clean usable C++ code so that if the project fails, the code is still salvageable in its C++ form.

It's not intended as a separate language.

Re: Soursop and Ponies in Kona: A C++ Committee Trip Report

#14

Post by boardwaalk »

saboot wrote: post #7

Still hoping for compile time introspection/reflection for class serialization. Whichever language implements it first (C++ or other) I'm all in on. I come from a scientific background, where running code on data gathering machines, and writing it out, then reading it back in later for analysis is 90% of what I do.

I’ve done this with libclang: parsing C++ with clang.cindex in Python, walking the AST for structs with the right annotation, and generating code to serialize/deserialize. All integrated into a build system so the dependency links are there. Obviously being built into the language would be way better, but if I was spending 90% of my time I would take any necessary steps.

Re: Soursop and Ponies in Kona: A C++ Committee Trip Report

#17

Post by pjmlp »

jvanderbot wrote: post #3

I would love to see a world in which a system is designed and built from multiple languages, so that the "right" tool could be used for each part. Does this even make sense? The modern distributed web seems to be leading us there. Slowly, slowly. I would also love to see a world where all C, C++ dependencies magically port themselves to Rust without FFI or a first-cut rewrite that a hobbyist did. 10-20 years maybe? U…

It only makes things slighly better, but Windows, Android, macOS, iOS, mbed, and plenty of others have enough C++ into them, even in kernel space.

And yes, it will either take decades to purge IT ecosystems from them, or they finally get some #pragma enable-bounds-checking, #pragma no-implicit-conversions (yes there are compiler specific ways to get things like this), and similar, so that they can stay in the game of safe computing.

Re: Soursop and Ponies in Kona: A C++ Committee Trip Report

#18

Post by pjmlp »

ape4 wrote: post #5

Herb's CppFront looks like the best hope for a clean C++ future

If anything, Circle would be it.

CppFront is just like Carbon and Val, with a completly different syntax, translating to C++ is just an implementation detail, he just markets in a different way given his position at ISO, most likely not to raise too many waves.

Re: Soursop and Ponies in Kona: A C++ Committee Trip Report

#19

Post by pjmlp »

Iamreadingthehn wrote: post #13
varajelle wrote: post #8

Earlier quoted context omitted.

CppFront is a different project entirely. It's like saying C++ is C's future

CppFront compiles to C++ and everything is intended to map to clean usable C++ code so that if the project fails, the code is still salvageable in its C++ form. It's not intended as a separate language.

I can do the same with Eiffel, so is Eiffel C++'s future?
Post reply on HN