Skip to content

Commit

Permalink
Link issue #3 in README
Browse files Browse the repository at this point in the history
  • Loading branch information
repi committed Jul 3, 2019
1 parent 5a87e78 commit 126c280
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ This repository contains 3 crates:
| [`physx-sys`](physx-sys/) | Unsafe bindings to the PhysX C++ API | [![Crates.io](https://img.shields.io/crates/v/physx-sys.svg)](https://crates.io/crates/physx-sys) [![Docs](https://docs.rs/physx-sys/badge.svg)](https://docs.rs/physx-sys) |
| [`physx-macros`](physx-macros/) | Utility macros used internally by the `physx` crate | [![Crates.io](https://img.shields.io/crates/v/physx-macros.svg)](https://crates.io/crates/physx-macros) [![Docs](https://docs.rs/physx-macros/badge.svg)](https://docs.rs/physx-macros) |

Our goal is that one should only use the safe Rust `physx` crate but it is still in early development and doesn't provide full coverage yet 🚧 (tracked in #3).
Our goal is that one should only use the safe Rust `physx` crate but it is still in early development and doesn't provide full coverage yet 🚧 (tracked in [#3](https://github.com/EmbarkStudios/physx-rs/issues/3)).

So right now one for certain features one can use it in conjunction with the unsafe and cumbersome `physx-sys` crate.

Expand Down

0 comments on commit 126c280

Please sign in to comment.