6 stable releases
2.2.0 | Jun 1, 2023 |
---|---|
2.1.0 | May 30, 2023 |
2.0.0 | May 30, 2023 |
1.1.0 | May 29, 2023 |
1.0.1 | May 28, 2023 |
#6 in #ranking
101 downloads per month
Used in 2 crates
49KB
1K
SLoC
Turn's Cock Tier Evaluator ๐ ๐
Library for Turn's Cock Tier Evaluator.
The Anatomy of the Evaluator ๐ ๐ฉบ
I've dissected the cock-rating task into neat, testable modules. Here's a quick breakdown:
- bin_use (mod bin_use): Responsible for anything in the library that is only intended to be used by external binaries such as
cock-cli
orcock-tui
. This currently holds aUserData
struct as well as aAppState
enum. - User (user.rs): You, the user, the cock-owner.
- CockStruct (cock_struct.rs): Your magnificent (or not so magnificient) monument's blueprint, combining all its noteworthy aspects into a single entity.
- CockHandler (cock_handler.rs): The gentle hands wrapping up the
User
andCockStruct
to provide easy methods to calculate and print all the juicy details about your member. - Traits (traits.rs): These aren't your cock traits, they're various Rust traits used throughout the application.
- Tier (tier.rs): Enum for letter grades.
- cock_parts (mod cock_parts): Each of these modules, like
size.rs
,aesthetic.rs
,balls.rs
(and others), represents a particular feature of your shlong, providing a score for several of them (a few features have no impact on ratings as of right now).
Optional Feature Modules
- bin_use (mod bin_use): Responsible for anything in the library that is only intended to be used by external binaries such as
cock-cli
orcock-tui
. This currently holds aUserData
struct as well as aAppState
enum.
Getting Rated and Library Usage ๐ ๐ต๏ธโโ๏ธ
Want to see where you stand in the land of peen, but you're kinda a dummy?! Luckily I'm here to guide you through the process.
The Binary Packages
cock-cli
: CLI App using thecock_lib
librarycock-tui
: TUI App using thecock_lib
librarycock-web
: COMING SOON - WEB BACK END FORcock_lib
The API
You're a developer who sees the inherent value in this? Strange. However, it is fairly simple to get started with things. To begin, add the following to your Cargo.toml
file:
[dependencies]
cock-lib = "x.x.x"
Below is an example of one way you could go about using the API to create a data structure representing a cock, otherwise known as a CockStruct
.
use cock_lib::{
CockStruct,
cock_parts::{Size, Aesthetic, Balls, Shape, Curvature, Circumcision, Veininess, Abnormalities, Inches}
};
let cock = CockStruct::new(
Size {
length: 5.5,
girth: 4.5,
size_type: Inches,
},
Aesthetic::Normal,
Balls::Normal,
Shape::Cylindrical,
Curvature::Straight,
Circumcision::Uncircumcised,
Veininess::Normal,
Abnormalities::None,
);
Testing ๐งซ ๐งช
This library comes with a built-in test suite that verifies the functionality of the code. To run the tests, use the command cargo test
in the project's root directory.
License ๐ ๐ผ
MIT License
Dependencies
~0.4โ1MB
~22K SLoC