This is a demo in how to slap a FastConfig on top of the struct and gives you load and save

[vaytea]

sorry about the delay
I have test and use this in my app, it works just fine.
tests are implemented
Docs are not ready

I was thinking about an attribute like #[fast_config(crate = "...")] to export the crate like serde in lower deps.

[FlooferLand]

Over-all a very welcome PR when you're done with it!
The derive macro makes working with fast_config way nicer, and you're using a lot of more modern Rust practices like default features (while I personally prefer not including every feature by default, I understand this seems to be preferred by most Rust users?)

This is still a draft, so as I understand it you'll continue to add to it until its ready for a proper review / merge, and from there on I'll be publishing the fast_config_derive crate as well.

I was thinking about an attribute like #[fast_config(crate = "...")] to export the crate like serde in lower deps.

I'm not sure what you mean specifically

[vaytea]

I have also added a new method to create the config directly from file

[FlooferLand]

Hi, thank you for the PR!

Looks great so far, however something seems quite odd to me. Was a part of this written by AI?

I'm mainly asking due to the broken GitHub README formatting in your fork, and some of the strange language in the comments, and the tests having very oddly named functions/variables.

---

---

(Usually mistakes like these would be spotted since they're front and center in your README)

It's somewhat messily formatted featuring inconsistent spacing between lines, includes the # marks usually used in Rust tests that would usually be spotted and removed, and tend to over-explain what's happening in the code via comments even in simple statements.

Not trying to accuse you for any reason, just wondering as your GitHub account is quite new and that's raising suspicions a bit, also wondering about your stance on AI.

I will be merging this regardless, as the code itself is well written outside some small mistakes I can easily correct, but I'm curious.

[FlooferLand]

Both crates are now published on crates.io!
Let me know if you encounter any bugs. All the tests passed, but I can't test how it'd actually work in real world scenarios compared to the old version right now.

I'd also appreciate a follow-up PR to add a load_or_default method that defaults and writes the default to the file instead of failing, as I believe calling load right now on a file that doesn't exist would return an error? I'm very busy at the moment so I can't check.

Again, thank you for the PR!

[vaytea]

Hi The English is not my native language And I used chatgpt for updating the readme. About the API I used the crate for mu project at work. I have about 10 to 15 crates to develop and maintain for the project so I create an crates to contain the basic traits and the basic dependencies for easier upgrade and maintain that is the reason for #[fast_config( crate = "..."). The new function is used for showing the user current contents of the config file for resetting any unwanted changes.

…

On Wed, Dec 10, 2025 at 3:58 AM FlooferLand! ***@***.***> wrote: *FlooferLand* left a comment (FlooferLand/fast_config#5) <#5 (comment)> Hi, thank you for the PR! Looks great so far, however something seems quite odd to me. Was a part of this written by AI? I'm mainly asking due to the broken GitHub README formatting in your fork, and some of the strange language in the comments. ------------------------------ image.png (view on web) <https://github.com/user-attachments/assets/f94ffdb9-f471-4176-9cc0-045eb07e09f9> ------------------------------ It's somewhat messily formatted featuring inconsistent spacing between lines, includes the # marks usually used in Rust tests that would usually be spotted and removed, and tend to over-explain what's happening in the code via comments even in simple statements. Not trying to accuse you for any reason, just wondering as your GitHub account is quite new and that's raising suspicions a bit, also wondering about your stance on AI — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAUR5ECU5V6J4A43JMNOVID4A5SJTAVCNFSM6AAAAACHVECQJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMZUHA2DKMJTGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[FlooferLand]

That's fair, thank you for your work!