Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderIt is great to have such a collection of rules and I hope they will be integrated into some easy-to-integrate static code analysis tool (as mentioned in the introduction). Maybe this will help people to transition to more modern C++ and to avoid some pitfalls (e.g. forgetting the "noexcept" for move constructors/assignments). However, in some respect this list also shows what is wrong with C++: The fact that you even need such a huge set of rules to write safe…
I wish they were more specific about when to use and not use exceptions. Truth be told I really hate exceptions and I strongly feel that they should only be used in the most disastrous situations. I'm messing with the 0MQ C++ wrapper now (which I will probably move off of) and they use exceptions for freaking everything. For example the send(msg) method returns true if the message is sent, false if EWOULDBLOCK is returned by the C api, or…
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 457
- Total comments
- 236
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking
Every submission
| Date | Title as submitted | By | Points | Comments |
|---|---|---|---|---|
| 2015-09-18 | C++ Core GuidelinesFirst breakout · Best thread | octoploid | 268 | 126 |
| 2015-09-30 | The C++ Core Guidelines have now a FAQ | ingve | 3 | 0 |
| 2016-09-12 | C++ Core Guidelines | adamnemecek | 3 | 0 |
| 2016-12-19 | C++ Core Guidelines | pthyme | 2 | 0 |
| 2018-03-09 | C++ Core GuidelinesHall induction · Latest 20+ point return | hamid914 | 179 | 110 |
| 2026-01-26 | C++ Core Guidelines | michaelsbradley | 2 | 0 |