trinitrix

bpeetz

trinitrix

forked from trinitrix/core

Fork 0

Author	SHA1	Message	Date
Benedikt Peetz	50d7948a2d	Build(Cargo): Update `Cargo.lock` and upgrade `Cargo.toml`	2023-07-09 08:41:25 +02:00
Benedikt Peetz	5e04ab49ee	Build(cargo): Remove wildcard version specification in `Cargo.toml` Wildcard version is comparable to selecting a version depending on the result of a dice roll. What I mean with this is, that the version will be selected based on what the specific user already has in their cargo registry. This means that the same codebase will compile wonderfully on one machine but will fail with weird errors like: `the trait 'From<crossterm::event::Event>' is not implemented for 'Input'` on an other one. Additionally crates.io does not accept crates with a bare wildcard version requirement for aforementioned reasons. Lastly using direct versions requirement allows to use `cargo upgrade` to automatically update these requirements to their highest possible value, as determined by SemVer. This works especially well, when adding new dependencies with `cargo add`, as this also adds a direct version requirement.	2023-07-09 08:38:59 +02:00
Benedikt Peetz	2905a0830a	Style(treewide): Format with rustfmt	2023-07-09 07:58:18 +02:00

Author

SHA1

Message

Date

Benedikt Peetz

50d7948a2d

Build(Cargo): Update `Cargo.lock` and upgrade `Cargo.toml`

2023-07-09 08:41:25 +02:00

Benedikt Peetz

5e04ab49ee

Build(cargo): Remove wildcard version specification in `Cargo.toml`

Wildcard version is comparable to selecting a version depending on
the result of a dice roll. What I mean with this is, that the version
will be selected based on what the specific user already has in their
cargo registry. This means that the same codebase will compile
wonderfully on one machine but will fail with weird errors like:
`the trait 'From<crossterm::event::Event>' is not implemented for 'Input'`
on an other one.

Additionally crates.io does not accept crates with a bare wildcard
version requirement for aforementioned reasons.

Lastly using direct versions requirement allows to use `cargo upgrade`
to automatically update these requirements to their highest possible
value, as determined by SemVer. This works especially well, when adding
new dependencies with `cargo add`, as this also adds a direct version
requirement.

2023-07-09 08:38:59 +02:00

Benedikt Peetz

2905a0830a

Style(treewide): Format with rustfmt

2023-07-09 07:58:18 +02:00

Compare commits

3 Commits

6aa8050b10 ... 50d7948a2d

Diff Content Not Available

Compare commits

3 Commits 6aa8050b10 ... 50d7948a2d

Diff Content Not Available

3 Commits

6aa8050b10 ... 50d7948a2d