this post was submitted on 01 Sep 2024
36 points (100.0% liked)

Learn Programming

1625 readers
1 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
Ategon@programming.dev
JaumeI@programming.dev
bugsmith@programming.dev
36
Is it better to check if a file exists before trying to load it, or to try to load it, and catch the error and move on? (lemmy.ml)
submitted 2 months ago by Binette@lemmy.ml to c/learn_programming@programming.dev
16 comments fedilink hide all child comments
 

For context, I am trying to do a save system for a game.

you are viewing a single comment's thread
view the rest of the comments
[–] lord_ryvan@ttrpg.network 3 points 2 months ago (1 children)

This depends quite a bit on your language and framework/filesystem-library. Could you add what those are?

[–] Binette@lemmy.ml 3 points 2 months ago (1 children)

I'm using Rust and Bevy, with bevy_moonshine for saving

[–] BatmanAoD@programming.dev 3 points 2 months ago

Do you mean moonshine_save? Does it even provide an API for loading that doesn't return a Result with a possible LoadError?

Rust doesn't generally "throw" errors, it returns them; and generally, function APIs will guide you in the right direction. You generally should not use unwrap() or expect() in your finished code (though the unwrap_or... variants are fine), which means that you must handle all errors the API can return programmatically (possibly just by propagating with ?, if you will instead be handling the error in the caller).