Preferences

nemetroid
Joined 3,884 karma
Currently employed by a large company.

  1. Yes, many or even most domains where C++ sees a large market share are domains with no other serious alternative. But this is an indictment of C++ and not praise. What it tells us is that when there are other viable options, C++ is rarely chosen.

    The number of such domains has gone down over time, and will probably continue to do so.

  2. You can throw in a destructor but not from one, as the quoted text rightly notes.
  3. The new profiling.sampling module looks very neat, but I don't see any way to enable/disable the profiler from code. This greatly limits the usefulness, as I am often in control of the code itself but not how it is launched.
  4. RHEL10 has been released and does require x86-64-v3.

    https://access.redhat.com/solutions/7066628

  5. Each entry in the map will be copied. In C++, const T& is allowed to bind to a temporary object (whose lifetime will be extended). So a new pair is implicitly constructed, and the reference binds to this object.
  6. Close, it is a std::pair, but it differs in constness. Iterating a std::map<K, V> yields std::pair<const K, V>, so you have:

      std::pair<const std::string, int>
    
    vs

      std::pair<std::string, int>
  7. > Both Microsoft and Google seem to do it just fine

    Microsoft sends me DMARC reports saying "yes, everything was accepted 100%, all good". The delivery logs on our end look good as well. However, they silently drop a large portion of messages with a Hotmail destination.

  8. A nice way to fix bugs is to make the buggy state impossible to represent. In cases where a bug was caused by some fundamental flaw in the original design, a redesign might be the only way to feel reasonably confident about the fix.
  9. You're right and I edited my comment.
  10. > The effect of referring to a copy of the object when locking, unlocking, or destroying it is undefined.

    https://pubs.opengroup.org/onlinepubs/9699919799/functions/V...

    I.e., if I pthread_mutex_init(&some_addr, ...), I cannot then copy the bits from some_addr to some_other_addr and then pthread_mutex_lock(&some_other_addr). Hence not movable.

    > Moving a mutex is otherwise non-sensical once the mutex is visible

    What does "visible" mean here? In Rust, in any circumstance where a move is possible, there are no other references to that object, hence it is safe to move.

  11. PLEASE mention INTERCAL!
  12. Did you read the essay?
  13. The article has an off-by-one error. There are 45 characters in the basic alphanumeric alphabet, and / is the missing one.
  14. The tracks on the Gothenburg side have since been removed, so even this workaround would not be possible today (they would have to go to Trelleborg instead).
  15. It is interesting though that when he mentions AI as one of the non-silver bullets, one of the arguments is that the AI models of the time were problem-specific and not easily transferable.
  16. Not really if they only ever do it for small, personal workspaces.
  17. By "western", do you mean American?
  18. Same in Gothenburg. There's a single underground station, with the platform in the middle, so the trams need to cross over. Another underground station is planned, but it will have the tracks in the middle instead.
  19. Maybe some preprocessing, maybe column generation, depends on the problem.
  20. GCC 12 is available for RHEL 7.
  21. > So not really a problem with Genshin's anticheat (indeed, users who had never played the game or even heard about it would be affected), but a problem with how antivirus providers dealt with it.

    The distinction doesn't really matter. The claim wasn't that the ransomware authors exploited deficiencies in the anticheat design, just that the anticheat was used to install the ransomware, which it was.

  22. I can't find it, but believe Joe Armstrong said something along those lines (but I think his number was ten).
  23. I'm sure someone did.
  24. Case insensitivity is a code smell?
  25. From the "detailed explanation" document (my emphasis):

    > When organising the release of packages, you may end up wanting to group several changes together written by different people and/or over a relatively large period of time. The best time to capture this information is when submitting a PR (when it is fresh in your mind), not when you eventually go to batch and release these changes.

    > Git is a bad place to store this information, as it discourages writing detailed change descriptions - you want to allow people to provide as much documentation for the change as they want.

    How does Git discourage writing detailed change descriptions? Is this a Github thing, i.e. the web UI workflows discourage it? I use Git a lot but barely use Github.

    https://github.com/changesets/changesets/blob/main/docs/deta...

  26. Looking at the Ikea US website, the Simrishamn and PS 2014 seem to have similar solutions: a plate that screws into an electrical box and provides a hook (the lowest common international denominator).

    What do you do if you want to move a ceiling light a bit to the side? Do you install an entire new electrical box?

  27. Never seen a light fixture that screws into the ceiling.
  28. A book with that title would surely be very different indeed.
  29. Sure, and the safe() function proposed upthread might also just be doing logging.

This user hasn’t submitted anything.

Keyboard Shortcuts

Story Lists

j
Next story
k
Previous story
Shift+j
Last story
Shift+k
First story
o Enter
Go to story URL
c
Go to comments
u
Go to author

Navigation

Shift+t
Go to top stories
Shift+n
Go to new stories
Shift+b
Go to best stories
Shift+a
Go to Ask HN
Shift+s
Go to Show HN

Miscellaneous

?
Show this modal