diff --git a/Cargo.toml b/Cargo.toml index 44668c6c..d6ab0988 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,9 +1,10 @@ [workspace] -members = ["mlx-macros", "mlx-sys", "mlx-rs"] +members = ["mlx-macros", "mlx-sys", "mlx-rs", "mlx-nn"] resolver = "2" [workspace.dependencies] mlx-sys = { version = "0.0.8", path = "mlx-sys" } -mlx-macros = { version = "0.1.0", path = "mlx-macros" } \ No newline at end of file +mlx-macros = { version = "0.1.0", path = "mlx-macros" } +mlx-rs = { version = "0.14.0", path = "mlx-rs" } \ No newline at end of file diff --git a/mlx-nn/Cargo.toml b/mlx-nn/Cargo.toml new file mode 100644 index 00000000..72b9a564 --- /dev/null +++ b/mlx-nn/Cargo.toml @@ -0,0 +1,7 @@ +[package] +name = "mlx-nn" +version = "0.1.0" +edition = "2021" + +[dependencies] +mlx-rs = { workspace = true } \ No newline at end of file diff --git a/mlx-nn/src/lib.rs b/mlx-nn/src/lib.rs new file mode 100644 index 00000000..8b137891 --- /dev/null +++ b/mlx-nn/src/lib.rs @@ -0,0 +1 @@ + diff --git a/mlx-rs/src/fft/mod.rs b/mlx-rs/src/fft/mod.rs index 8d18e00d..1d9c910d 100644 --- a/mlx-rs/src/fft/mod.rs +++ b/mlx-rs/src/fft/mod.rs @@ -7,12 +7,12 @@ //! The difference are explained below using `fftn` as an example: //! //! 1. `fftn_unchecked`/`fftn_device_unchecked`: This function is simply a wrapper around the C API -//! and does not perform any checks on the input. It may panic or get an fatal error that cannot -//! be caught by the rust runtime if the input is invalid. +//! and does not perform any checks on the input. It may panic or get an fatal error that cannot +//! be caught by the rust runtime if the input is invalid. //! 2. `try_fftn`/`try_fftn_device`: This function performs checks on the input and returns a -//! `Result` instead of panicking. +//! `Result` instead of panicking. //! 3. `fftn`/`fftn_device`: This function is a wrapper around `try_fftn` and unwraps the result. It -//! panics if the input is invalid. +//! panics if the input is invalid. //! //! The functions that contains `device` in their name are meant to be used with a user-specified //! `StreamOrDevice`. If you don't care about the stream, you can use the functions without `device`