Show HN: C++ Compiler Support Page
11–20 of 32 posts
Re: Show HN: C++ Compiler Support Page
#12Feature names tend not to be very approachable. They often use very precise terminology or refer to papers with names that are targeted for a very in-the-know population.
As an example, one of the features listed is '`constexpr` `std::shared_ptr` and friends'. You seem to have a search that can cope with backticks but this feature doesn't show up if I search for 'constexpr shared_ptr'. That can be solved technically, but the bigger problem is that this feature also changes things for `weak_ptr` - or 'smart pointers' as a concept.
I can't picture a situation where I end up wanting to know the status of that feature's implementation in isolation.
For what it's worth, cppreference isn't any better at this, since it doesn't have any notes on the addition of support for `constexpr`ness of either pointer type. But with enough will I can change that.
Re: Show HN: C++ Compiler Support Page
#13Nice! Just curious about one aspect: how much demand is there for C++ nowadays for new projects and what is the anticipated demand mid to long term [5+ years]? Asking as I am seriously considering if it would be a good idea to transition to C++ development (professionally, not as a hobby). Wondering if it would make sense from the POV of projected/anticipated future demand, job security and salaries ( VERY important)…
Re: Show HN: C++ Compiler Support Page
#14Is it possible to generate this automatically using conformance tests?
You're not going to find some hobbyist coming up with a useful conformance or coverage test suite for free. It's intensive, expensive, and arduous.
Such things are mandatory, however, if you are a C++ vendor targeting ISO 26262 or IEC 61508 or similar -- basically, software that could kill you if it's done wrong. It's a niche with money and motivation.
Re: Show HN: C++ Compiler Support Page
#15Re: Show HN: C++ Compiler Support Page
#16Re: Show HN: C++ Compiler Support Page
#17Personally I am not not sure the live search on this new page saves me time, but perhaps if you added the ability to only show missing features it could be useful. For example if I could pick that I am interested in c++23 and earlier and that I use gcc-14 and clang-16 it should list the features that won't work for me. That would be useful compared to trying to scan the full list.
Re: Show HN: C++ Compiler Support Page
#18Nice! Just curious about one aspect: how much demand is there for C++ nowadays for new projects and what is the anticipated demand mid to long term [5+ years]? Asking as I am seriously considering if it would be a good idea to transition to C++ development (professionally, not as a hobby). Wondering if it would make sense from the POV of projected/anticipated future demand, job security and salaries ( VERY important)…
There are not enough oldtimers alive to do it, and the younger guys refuse to learn it. That drove up the hourly salaries enormously.
Re: Show HN: C++ Compiler Support Page
#19Any specific reason on why the project is closed source?
Re: Show HN: C++ Compiler Support Page
#20Very handy, I love it. Linking the pertaining proposals is the pinnacle, since they explain each feature in detail.