Achieve compile-time unit correctness and avoid runtime surprises.
Use units as types, to document your functions, and convert to units of the same dimension:
const units = @import("unitz").quantities(f32);
const m = units.meter;
const s = units.second;
const kt = units.knot;
const @"km/h" = unitz.evalQuantity(f32, "km / h", .{});
fn aircraft_speed(distance: m, duration: s) kt {
const speed = distance.div(duration); // value is in m/s
const result = speed.to(kt);
std.debug.print("Speed: {} m/s = {} kt = {} km/h\n", .{
speed.val(),
result.val(),
speed.to_val(@"km/h"),
});
return result;
}
A compilation error occurs when trying to perform an invalid conversion:
const J = units.joule;
const hp = units.imperial_horsepower;
const engine_power = hp.init(130);
const energy = engine_power.to(J);
Will result in the compilation error:
src/root.zig:233:61: error: Units are only interconvertible if they measure the same kind of dimension
comptime if (!unit_from.is_compatible(unit_to)) @compileError("Units are only interconvertible if they measure the same kind of dimension");
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
foo.zig:29:35: note: called from here
const energy = engine_power.to(J);
~~~~~~~~~~~~~~~^~~
No conversion is done implicitly, the value stored in memory is exactly the one provided to the constructor.
This library does not provide all variations of standard units: meter and hour are provided, but kilometer and kilometer per hour is not. Instead, you can define any unit you want from its definition, using prefixes if needed:
const nanosecond = unitz.evalQuantity(f32, "ns", .{});
const @"kg/m3" = unitz.evalQuantity(f32, "kg / m^3", .{});
const kilowatthour = unitz.evalQuantity(f32, "kW * h", .{});
const Cal = unitz.evalQuantity(f32, "kcal", .{}); // large calorie
const std = @import("std");
const unitz = @import("unitz");
const q = unitz.quantities(f32);
const m = q.meter;
const kg = q.kilogram;
const lb = q.pound;
const cm = unitz.evalQuantity(f32, "cm", .{});
const @"kg/m²" = unitz.evalQuantity(f32, "kg / m^2", .{});
fn body_mass_index(height: m, weight: kg) @"kg/m²" {
return weight.div(height.pow(2));
}
pub fn main() void {
const height = cm.init(162);
const weight = lb.init(124);
const bmi = body_mass_index(height.to(m), weight.to(kg));
std.debug.print("BMI: {}", .{bmi.val()});
}
const unitz = @import("unitz");
const slug = unitz.evalUnit("32.174_049 * lb", .{});
const lbf = unitz.evalQuantity(f32, "ft * slug / s^2", .{ .slug = slug });
const @"lbf.s" = unitz.evalQuantity(f32, "lbf * s", .{ .lbf = lbf.unit });
const @"N.s" = unitz.evalQuantity(f32, "N * s", .{});
const @"μs" = unitz.evalQuantity(f32, "us", .{});
fn compute_impulse(force: lbf, delta: @"μs") @"lbf.s" {
return force.mul(delta).to(@"lbf.s"); // we need to convert from lbf.us to lbf.s, if we forget, a \
compilation error occurs
}
fn compute_trajectory(impulse: @"N.s") void {
// ...
}
pub fn main() void {
const force = lbf.init(123.0);
const delta = @"μs".init(45.0);
compute_trajectory(compute_impulse(force, delta)); // compilation error ! Adding .to(@"N.s") will \
fix it
}
And just like that, you can avoid crashing into the atmosphere
Add the dependency in your build.zig.zon by running the following command:
zig fetch --save git+https://github.com/agagniere/unitz#master
Add it to your exe in your build.zig:
exe.root_module.addImport("unitz", b.dependency("unitz", .{ .target = target, .optimize = optimize }).module("unitz"));
Then you can import it from your code:
const unitz = @import("unitz");
zig build docs
# Then serve locally, for example:
python -m http.server 8000 -d zig-out/docs
open "http://localhost:8000"
zig fetch --save git+https://github.com/InKryption/comath#main