[–] 2 points 1 month ago

I don't know, it looks like the amount of issues is way higher than improvement in comfort. Beside, they mentioned a lot of corner cases that would definitely show up and become a problem

I've been using C++ for quite some time, and it also had some talks about having named parameters, but it only helps in some places and hinders in most, imo. I feel like in Rust you may use a struct as parameter containing all of function parameteres where you really want the names

  • source
  • parent
  • context
  • [–] 1 point 1 month ago

    I'm guessing, they mean the user of a future that already exists as it is, what you mean is you can implement a future that would provide a way for the code inside to know of being cancelled. But most of the time you don't do that, and a function that was polled once and then dropped will never know about that

  • source
  • parent
  • context
  • view more: ‹ prev next ›