#simple #vector #mathematics #no-std

nightly coord

A simple, ergonomic vector mathematics crate

16 releases (10 breaking)

Uses old Rust 2015

0.11.1 Oct 24, 2019
0.11.0 Jul 4, 2018
0.10.1 Jul 4, 2018

#682 in Math

Download history 7/week @ 2023-06-09 23/week @ 2023-06-16 31/week @ 2023-06-23 39/week @ 2023-06-30 26/week @ 2023-07-07 17/week @ 2023-07-14 21/week @ 2023-07-21 10/week @ 2023-07-28 12/week @ 2023-08-04 13/week @ 2023-08-11 22/week @ 2023-08-18 27/week @ 2023-08-25 31/week @ 2023-09-01 28/week @ 2023-09-08 13/week @ 2023-09-15 4/week @ 2023-09-22

77 downloads per month

MIT license

1.5K SLoC

coord is deprecated. I recommend using vek, a project with near-identical aims instead.

Coord Coord

Build Status Crates.io Downloads Docs


Coord is a simple, ergonomic vector mathematics crate for Rust designed for use in game development, physics engines and other programs that deal with general-purpose multi-variable mathematics.

Coord is now no_std compatible!


extern crate coord;
use coord::prelude::*;

fn main() {
	// Coord supports 4 multi-variable vector types: Vec1, Vec2, Vec3 and Vec4
	let mut v = vec3!(1.0, 2.5, 3.0);

	// Coord supports common mathematical operations for both primitive and vector types
	v += vec3![1.0; 3] * 5.0;
	let _ = v * vec3!([10.0, 10.0, 10.0]);

	// Coord implements many common mathematic functions
	let _ = v.length();
	let _ = v.norm();

	// Coord supports debug and display printing of vectors
	println!("Debug => {:?}", v);
	println!("Display => {}", v);

	// Coord allows arbitrary vector component types
	let _ = vec2!(true, false); // Create a boolean vector

For more examples, visit https://docs.rs/coord


  • Generic Vec1, Vec2, Vec3 and Vec4 types
  • Utility macros to make vector manipulation simpler
  • VecXu, VecXi and VecXf default type definitions
  • Basic mathematic operations (Add, Sub, Mul, Div)
  • Mathematic functions (i.e: .length(), .norm(), etc.)
  • Serialization support with the serialize feature
  • 64 bit default type support with the large_defaults feature
  • Hash support
  • .map() method performing arbitrary element-wise vector transformation
  • .convert_to() method allowing element-wise vector conversion
  • .div_floor() method allowing floor-like vector division

Coming Soon

  • Bitwise operations
  • More mathematic functions
  • Modulo operator for integer vector types

Using Coord

To use Coord in your Rust project, add the following line beneath the [dependencies] section in your Cargo.toml file.

coord = "0.11.0"

If you want to enable serialization or 64-bit defaults, you should specify the dependency like the following line instead.

version = "0.7.0"
features = ["serialize", "large_defaults"]


Why does Coord exist?

Coord came about as a result of a general dissatisfaction with existing vector mathematics libraries during development of the Veloren Project. Existing solutions were either too complicated, awkward to use, or required too many dependencies.

Does Coord aim to eventually implement feature X?

Coord does not aim to be a fully-blown N-dimensional mathematics library. It aims to implement a small yet elegant set of features that make it suitable for applications where simple multi-variable mathematics is required.

If you think feature X falls within that scope, and is not yet on the project todo list, you can open an issue on GitHub and I'll consider implementing it.

Why does Coord choose 32 bit values for its default types?

Coord defines a set of 'default' types within the defaults module. They are included within the prelude module too. These default types, such as Vec2f, Vec3u, Vec4b, etc. exist to make writing code with Coord faster. It is still possible to program without them like Vec2<f32>, Vec3<u32>, Vec4<bool>, etc. Coord chooses 32-bit types by default because it is my belief that these are more useful when developing for games and physics engines, which require fast calculations. Additionally, 32 bit floating point types means that Coord is compatible with OpenGL.

Why does Coord not have a general-purpose vec! macro?

Such a macro would conflict with the vec! macro within Rust's standard library.

Why does Coord not rely on the standard library?

It doesn't need to. Why limit the use cases of the library by requiring std?

Bug! Bug! I've found a bug!

Open an issue on Github and I'll fix it as soon as possible.

You can open an issue here


Coord is open source software, licensed under the MIT license (See 'LICENSE' or http://opensource.org/licenses/MIT)