Robert Garrett
5cc0b49cd9
I get lazy with commits when following guided material. There's a design challenge to approach, now. I'm saving here so I can revert changes in case it goes sideways. Materials are proving to be a little complicated in Rust semantics. The Ray Tracing in a Weekend book uses shared_ptr's, but Rust doesn't really like that. I'm doing references with lifetime annotations. Hopefully I can get that the right way around to work out. The materials themselves look like reasonable candidates for describing as Enums. This takes away the ability to add new ones by simply impl'ing a trait, but that was never gonna happen anyway. The code would be modified and recompiled. There's no difference in maintenance cost if that's a new struct impl'ing a trait, or adding enum members.
11 lines
231 B
TOML
11 lines
231 B
TOML
[package]
|
|
name = "rustpt"
|
|
version = "0.1.0"
|
|
edition = "2021"
|
|
|
|
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
|
|
|
|
[dependencies]
|
|
rand = { version = "0.8.5", features = ["small_rng"] }
|
|
|