[package]
# This package only contains a binary crate named crates
# A package can have multiple binary crated by placing files in the src/bin directory: each file will be a seperate binary crate
# There is no mention of src/main.rs because Cargo considers src/main.rs as the crate root of a binary crate with the same name as the package
# If the package directory contains src/lib.rs, the package contains a library crate with the same name as the package

# A binary crate should generate an executable (or multiple) that can be installed in the user's path and can be executed as usual
# A library crate is a library of reusable components that is meant to be included in another library or binary crate

# Why only one library allowed for a package?
# Cargo is a package manager, so its primary role is to define a library. 
# When using a crate as a dependency, we only specify the package name in cargo.toml
# Since there can be at most one library, Cargo doesnt need us to specify which one to use
name = "crates_tlietz_test_publish"
version = "0.1.0"
edition = "2021"
description = "Hello Rustaceans!"
license = "MIT OR Apache-2.0"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]

# Modules let us organize code within a crate into groups for readability and easy reuse.
# Modules also controls the privacy of items