Release 0.1.1

CHANGELOG.md

@@ -10,11 +10,14 @@ Note: In this file, do not use the hard wrap in the middle of a sentence for com
 
 ## [Unreleased]
 
+## [0.1.1] - 2022-02-13
+
 - Fix "unsupported operation: unable to turn pointer into raw bytes" Miri error. ([#1](https://github.com/taiki-e/atomic-memcpy/pull/1))
 
 ## [0.1.0] - 2022-02-12
 
 Initial release
 
-[Unreleased]: https://github.com/taiki-e/atomic-memcpy/compare/v0.1.0...HEAD
+[Unreleased]: https://github.com/taiki-e/atomic-memcpy/compare/v0.1.1...HEAD
+[0.1.1]: https://github.com/taiki-e/atomic-memcpy/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/taiki-e/atomic-memcpy/releases/tag/v0.1.0

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "atomic-memcpy"
-version = "0.1.0"
+version = "0.1.1"
 edition = "2018"
 rust-version = "1.36"
 license = "Apache-2.0 OR MIT"

README.md

@@ -21,7 +21,7 @@ See [P1478R1][p1478r1] for more.
 - If the type being copied contains uninitialized bytes (e.g., padding), it is incompatible with `-Zmiri-check-number-validity`. This will probably not be resolved until something like `AtomicMaybeUninit` is supported. **Note**: Due to [Miri cannot track uninitialized bytes on a per byte basis for partially initialized scalars][rust-lang/rust#69488], Miri may report this case as an access to an uninitialized byte, regardless of whether the uninitialized byte is actually accessed or not.
 
 [p1478r1]: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1478r1.html
-[implementation]: https://github.com/taiki-e/atomic-memcpy/blob/279d7041e48fae0943a50102ebab97e7ed3977ae/src/lib.rs#L359-L403
+[implementation]: https://github.com/taiki-e/atomic-memcpy/blob/fd3bd1ef0c7377422714399c0d1b84a5be8c0a00/src/lib.rs#L381-L427
 [asm-test]: tests/asm-test/asm
 [rust-lang/rust#69488]: https://github.com/rust-lang/rust/issues/69488