···1818*.pdb
19192020# End of https://www.toptal.com/developers/gitignore/api/rust
2121+2222+2323+# Added by cargo
2424+2525+/target
+26
Cargo.toml
···11+[package]
22+name = "dice-wire"
33+version = "0.1.0"
44+edition = "2024"
55+66+[lib]
77+crate-type = ["cdylib", "rlib"]
88+99+[features]
1010+default = ["console_error_panic_hook"]
1111+1212+[dependencies]
1313+wasm-bindgen = "0.2.84"
1414+1515+# The `console_error_panic_hook` crate provides better debugging of panics by
1616+# logging them with `console.error`. This is great for development, but requires
1717+# all the `std::fmt` and `std::panicking` infrastructure, so isn't great for
1818+# code size when deploying.
1919+console_error_panic_hook = { version = "0.1.7", optional = true }
2020+2121+[dev-dependencies]
2222+wasm-bindgen-test = "0.3.34"
2323+2424+[profile.release]
2525+# Tell `rustc` to optimize for small code size.
2626+opt-level = "s"
···11+pub fn set_panic_hook() {
22+ // When the `console_error_panic_hook` feature is enabled, we can call the
33+ // `set_panic_hook` function at least once during initialization, and then
44+ // we will get better error messages if our code ever panics.
55+ //
66+ // For more details see
77+ // https://github.com/rustwasm/console_error_panic_hook#readme
88+ #[cfg(feature = "console_error_panic_hook")]
99+ console_error_panic_hook::set_once();
1010+}