Skip to content

Commit

Permalink
Remove outdated Abomonable notion
Browse files Browse the repository at this point in the history
  • Loading branch information
HadrienG2 committed Sep 26, 2019
1 parent b5f7b71 commit e4a4963
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ Be warned that these numbers are not *goodput*, but rather the total number of b

## unsafe_abomonate!

Abomonation comes with the `unsafe_abomonate!` macro implementing `Abomonation` for structs which are essentially equivalent to a tuple of other `Abomonable` types. To use the macro, you must put the `#[macro_use]` modifier before `extern crate abomonation;`.
Abomonation comes with the `unsafe_abomonate!` macro implementing `Abomonation` for structs which are essentially equivalent to a tuple of other `Abomonation` types. To use the macro, you must put the `#[macro_use]` modifier before `extern crate abomonation;`.

Please note that `unsafe_abomonate!` synthesizes unsafe implementations of `Abomonation`, and it is should be considered unsafe to invoke.

Expand Down Expand Up @@ -82,4 +82,4 @@ if let Some((result, remaining)) = unsafe { decode::<MyStruct>(&mut bytes) } {
}
```

Be warned that implementing `Abomonable` for types can be a giant disaster and is entirely discouraged.
Be warned that implementing `Abomonation` for types can be a giant disaster and is entirely discouraged.

0 comments on commit e4a4963

Please sign in to comment.