Crates.io | mini-config-derive |
lib.rs | mini-config-derive |
version | 0.1.2 |
source | src |
created_at | 2023-04-17 19:22:08.460854 |
updated_at | 2024-04-29 08:13:36.944124 |
description | A supportive mini config derive macro |
homepage | |
repository | https://github.com/zonblade/mini-config-rs |
max_upload_size | |
id | 841820 |
size | 4,254 |
Minimalistic Dynamic Config for Rust
memory enhancement "again", tested with 32 million get simultaneously only consume 1.009 KB.
added new feature get_str()
to get by refrence (reduce 2x from get()
because of double String usage)
now it's only 1x usage of String
SomeEnum::Data.get_str() -> &str
no breaking changes introduced from 0.1.2, you can upgrade without worries!
i've tired to try rust config out there. but it's too big and heavy for my small project.
and for some reason, there is much feature which i did not use at all.
so i decided to create a minimalistic config which uses enum to store data into memory.
and retrive it using enum directly.
please add derive feature into Cargo.toml
to enable Configure
derive.
[dependencies]
mini-config = { version="*", features=["derive"]}
it can be used directly on main.
use mini_config::Configure;
// Debug and Clone "MUST" present.
#[derive(Debug,Clone,Configure)]
pub enum SampleConfig {
VariableOne
}
fn main(){
// set value (as &str)
SampleConfig::VariableOne.set("string");
// get value (as String)
let retrived_value = SampleConfig::VariableOne.val();
}
if you want to call it in other function? just import the enum.
use crate::SampleConfig;
and you good to go using .set("new val")
if you want to re-initialize
or .val()
if you want to get the data in that particular function.
best practice? please refer to example
folder at github repository.