dusa_collection_utils
| Crates.io | dusa_collection_utils |
| lib.rs | dusa_collection_utils |
| version | |
| source | src |
| created_at | 2024-07-15 19:30:22.43417+00 |
| updated_at | 2025-05-09 04:15:03.380102+00 |
| description | A common library with standardized functions that the ais_platform, dusa, recs and others will depend on |
| homepage | |
| repository | |
| max_upload_size | |
| id | 1304243 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Darrion Whitfield (Dj-Codeman)
documentation
README
Why is this
I have a few existing rust progects sact (superuser act) and rest (new encore) that share alot of similar code... This is the code. There will be another one like this just to keep code organize and seperate. This also allow be to update diffrent components with a cargo build as oppose to having to change the same file multiple times.
This lib has shared function across most of my projects.