you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 3 days ago (2 children)

convenience, developer experience. Ergonomics basically.

Can you point the notable relevant inconvenience, bad developer experience, and poor ergonomics developers are suffering from?

Is it all caused by a lock() method returning a Result?
Anything else?

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 2 points 2 days ago (1 child)

    Yes? I think I am done with this conversation. If you don't think this is a problem, we just disagree. Just move on, you don't have to convince everyone else who's been discussing this problem for years that it isn't a problem.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 0 points 2 days ago

    everyone else who’s been discussing this problem for years that it isn’t a problem.

    I haven't seen anyone else concede the performance talking point (under different banners), but proceeding to make this out to be a big issue. This includes this thread's OP which literally starts on-topic arguments with:

    How poisoning harms every single piece of code

    As discussed in too much detail above, (un)locking mutexes is cheap as long as they’re not contended, and when contended, they are at least cheap instruction wise. This is where poisoning mutexes get you.

    This is what makes your positioning weird.

    My replies here, starting with pointing out the lack of benchmarks of real-world use-cases, come from actually bothering to read OP, IN FULL.

  • source
  • parent