Skip to content

Commit

Permalink
Delete "no unsafe" claim from readme
Browse files Browse the repository at this point in the history
"No unsafe" is misleading because there is unsafe code unconditionally
compiled into the crate.

It looks like this sentence in the readme was written in 408f42a and
"no unsafe" was true at that point, but then 48 hours later some unsafe
code was added in 8904b5e and has been there ever since. It seems like
an oversight that the readme was not updated.
  • Loading branch information
dtolnay authored and jam1garner committed Jul 13, 2022
1 parent fcbc41a commit 864dcc9
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 @@ -33,7 +33,7 @@ A zero-allocation no_std-compatible zero-cost way to add color to your Rust term
* [x] Truecolor support (modern, 48-bit color)
* [x] Styling (underline, strikethrough, etc)

owo-colors is also more-or-less a drop-in replacement for [colored](https://crates.io/crates/colored), allowing colored to work in a no_std environment. No allocations, unsafe, or dependencies required because embedded systems deserve to be pretty too uwu.
owo-colors is also more-or-less a drop-in replacement for [colored](https://crates.io/crates/colored), allowing colored to work in a no_std environment. No allocations or dependencies required because embedded systems deserve to be pretty too uwu.

To add to your Cargo.toml:
```toml
Expand Down

0 comments on commit 864dcc9

Please sign in to comment.