Live data from Hacker News

Viewing profile — bingo3131

bingo3131

HN member
Joined
Sat, Jan 22, 2022, 11:34 AM UTC
HN karma
68
Public activity
22 items

About bingo3131

No profile information was provided.

Recent public activity

  1. comment
    Comment #43726893

    No idea how it works in other countries but in the UK there are fixed-rate mortgages and variable-rate mortgages. Fixed rate ones are where the interest rate is locked in at the ti…

  2. comment
    Comment #43726854

    I would assume it would be because the poster would find themselves in negative equity (depending on how much was left to repay on the mortgage) with all the potential pitfalls tha…

  3. comment
    Comment #42520510

    ! is commonly used as the unary not operator, so "a != b" makes sense as a shortcut for "!(a == b)". a not equals b.

  4. comment
    Comment #40851332

    FYI: this is the latest draft of the proposal and it has not been voted into C++26 yet, but it is getting close.

  5. comment
    Comment #40420297

    Rumour has it (not sure if this was ever confirmed) that one of the big reasons the second Xbox was called the Xbox 360 was to avoid unfavourable number comparisons with Sony. The …

  6. comment
    Comment #40301136

    A lot of programmers refer to the compiler explorer as Godbolt due to the domain name, such as saying "Godbolt link", "try it on Godbolt", etc. They do not realise that the domain …

  7. comment
    Comment #40295677

    For those who missed it: each item on the iceberg is actually a link that explains the topic in more detail.

  8. comment
    Comment #40295655

    Calling it a hint is very much over-simplifying things as there are also restrictions on what a constexpr function is and is not allowed to do, although those restrictions become f…

  9. comment
  10. comment
    Comment #39940806

    Regarding new/delete elision: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p09... You can also specify custom new/delete operations for your co-routine for control. I a…

  11. comment
    Comment #39936719

    It is undefined behaviour to modify objects declared as const (except if those objects have mutable members, in which case the mutable members can be modified). const int a = 1; If…

  12. comment
    Comment #39936634

    A post about an obscure C++ feature on Hacker News? Comments are going to be a dumpster-fire as usual. https://en.cppreference.com/w/cpp/utility/launder "template [[nodiscard]] con…

  13. comment
    Comment #39581978

    Misleading title? This is a Windows API bug with the slim reader/writer (SRW) locks. It's just that the bug was discovered via std::shared_mutex as that is implemented using SRW lo…

  14. comment
    Comment #38775007

    A new version of C++ comes out every 3 years, and every 3 years you will get loads of blog posts giving overviews of the changes as well as YouTube videos of conference talks on di…

  15. comment
    Comment #38774862

    Yes. The main feature this is built upon is C++20's new string formatting features (very heavily inspired by the third party libfmt). C++23 just adds convinience functions to forma…

  16. comment
    Comment #38446292

    It's being actively worked on for C++2x. This video is a fairly recent update on how it's progressing: https://www.youtube.com/watch?v=AoLl_ZZqyOk Note for those who are not used t…

  17. comment
    Comment #35473940

    https://en.wikipedia.org/wiki/GLib

  18. comment
  19. comment
    Comment #34244653

    I just made a new empty C++ project in MSVC 2022 and by default it generates compile options for both 32-bit and 64-bit, with 64-bit selected by default. The preprocessor mode can …

  20. comment
    Comment #30036106

    The issue is that code outside of some_func does not know that f has been destroyed and a new object created in the same memory location, thus wouldn't know that the const member f…

  21. comment
    Comment #30035888

    It is UB as the original object has non-static data members that are const-qualified.

  22. comment
    Comment #30035848

    foo::x is declared const inside the struct in the example given. Because of this, regardles of how you access foo::x, it will always be const.