• 0 Posts
  • 33 Comments
Joined 1 year ago
cake
Cake day: July 15th, 2023

help-circle
  • I think a better solution would be to add a method called something like ulock that does a combined lock and unwrap.

    My concern with lock+unwrap is only partly because of convenience; I also didn’t like it because I think it’s a bad idea to get people used to casually calling unwrap, because it tends to hide inadequate error handing.

    Now that I think about it, I don’t like how unwrap can signal either “I know this can’t fail”, “the possible error states are too rare to care about” or “I can’t be bothered with real error handing right now”. In one or two of those cases you want to leave it in my production code, and in the last you want to audit all instances and replace them with proper error handing. Using the same function for all three cases makes that difficult.



  • Looks like the author missed my main complaint about Rust mutexes, which is that the lock method returns a Result. There should be a try_unlock method for when someone actually wants to handle the rather obscure failure case, and the name lock should be used for a method that panics on failure but returns a value that doesn’t need to be unwrapped first. I see the current arrangement as being about as sensible as having array subscripting return a Result to handle the case of a failed bounds check.















  • lolcatnip@reddthat.comtoMemes@lemmy.mlThe line war has begun
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 month ago

    It would, however, seem like a straight line to whoever was on the boat, because they’d be traveling due west the whole time, and the course corrections they’d have to make to keep going west would look the same as course corrections needed to account for wind, ocean currents, etc.