Removed unsafe

[Enn3Developer]

This pr resolves #15.
A lot of things needed to change but for the better.
First of all, I needed to add the lazy_static dependency, I used it to instantiate and hold all the data.
Then, I implemented a struct containing all the data and getters for it, that struct has even a convenient function for adding things to the output code.
I wrapped that struct inside a RwLock, if in the future the need arises (the other option was Mutex).
I created lib.rs that contains mods and macros and removed the arg macro as it is useless at this point (there's no more need for unsafe)
I added a configuration file for clippy because it was angry that EnvData::set_data had 10 arguments, 3 more of the max he tolerated.

[Maiori44]

how does this impact performance? Does it slow it down or speed it up?

[Enn3Developer]

It seems to be the same, but there should be an overhead when getting the lock

[Maiori44]

and when does that happen?

[Enn3Developer]

when calling ENV_DATA.read() or ENV_DATA.write()

[Maiori44]

okay, I guess it's fine, I have 2 more questions:

• wouldn't it be better to call panic!() once instead of .expect() every time?
• shouldn't this pr be merged in the next branch instead?

[Enn3Developer]

.expect() calls panic!() under the hood
about the branch, I don't know the differences between the two

[Maiori44]

.expect() calls panic!() under the hood
I know, but if we call panic directly in the functions themselves I think we could save some memory in the exe?
about the branch, I don't know the differences between the two
the next branch is to be used for updates, the main branch should be updated when a new update is out (merging it with the next branch) or for small patches since the next branch is not necessary for those

[Enn3Developer]

I know, but if we call panic directly in the functions themselves I think we could save some memory in the exe?

pub const fn expect(self, msg: &str) -> T {
    match self {
        Some(val) => val,
        None => expect_failed(msg),
    }
}

Either we do this in the code or call it through .expect() is the same (expect_failed directly calls panic)

the next branch is to be used for updates
Should I remake the pr for that branch?

[Maiori44]

I guess we can keep .expect() then

Should I remake the pr for that branch?

yeah

[Enn3Developer]

Closing to make the pr in the other branch