trangar / periodic_table Goto Github PK

https://upload.wikimedia.org/wikipedia/commons/b/b5/NuclideMap_stitched.png

When deploying cargo, we get the following error:

error: failed to verify package tarball

Caused by:
  Source directory was modified by build.rs during cargo publish. Build scripts should not modify anything outside of OUT_DIR.
Added: /home/trangar/development/rust/periodic_table/target/package/periodic_table-0.2.0/src/lib.rs

To proceed despite this, pass the `--no-verify` flag.

It would be nice if the build script wrote to OUT_DIR, and we had a normal lib.rs that included it with include!(concat!(env!("OUT_DIR"), "/elements.rs"));

• Move src/main.rs to src/bin/generate.rs
• Move the generated file to src/generated.rs
• Parse the CSV directly into a CsvElement type that implements Debug to generate Element code
• Introduce lazy_static!

Field type improvements

• Symbol as an enum
• Parse atomic_mass into an enum or struct
• hex_colour can be just a (u8, u8, u8).
• Parse electronic_configuration into an enum or struct
• bonding_type can be an enum
• group_block can be an enum

Field description

• atomic_number
• symbol
• name
• atomic_mass
• cpk_hex_color
• electronic_configuration
• electronegativity
• atomic_radius
• ion_radius
• van_del_waals_radius
• ionization_energy
• electron_affinity
• oxidation_states
• standard_state
• bonding_type
• melting_point (reference pressure)
• boiling_point (reference pressure)
• density
• group_block
• year_discovered

It would be convenient if we could access each atom through an identifier, for example like periodic_table::atoms::H and periodic_table::atoms::Ga .

It would be nice if we could obtain physical quantities as f64, or a struct that contains both the value and an uncertainty.