Adding upstream version 86.0.1.upstream/86.0.1upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 52 insertions, 0 deletions

diff --git a/third_party/rust/num-iter/RELEASES.md b/third_party/rust/num-iter/RELEASES.md
new file mode 100644
index 0000000000..e1e849c756
--- /dev/null
+++ b/third_party/rust/num-iter/RELEASES.md
@@ -0,0 +1,52 @@
+# Release 0.1.39 (2019-05-21)
+
+- [Fixed feature detection on `no_std` targets][11].
+
+**Contributors**: @cuviper
+
+[11]: https://github.com/rust-num/num-iter/pull/11
+
+# Release 0.1.38 (2019-05-20)
+
+- Maintenance update -- no functional changes.
+
+**Contributors**: @cuviper, @ignatenkobrain
+
+# Release 0.1.37 (2018-05-11)
+
+- [Support for 128-bit integers is now automatically detected and enabled.][5]
+  Setting the `i128` crate feature now causes the build script to panic if such
+  support is not detected.
+
+**Contributors**: @cuviper
+
+[5]: https://github.com/rust-num/num-iter/pull/5
+
+# Release 0.1.36 (2018-05-10)
+
+- [The iterators are now implemented for `i128` and `u128`][7] starting with
+  Rust 1.26, enabled by the new `i128` crate feature.
+
+**Contributors**: @cuviper
+
+[4]: https://github.com/rust-num/num-iter/pull/4
+
+# Release 0.1.35 (2018-02-06)
+
+- [num-iter now has its own source repository][num-356] at [rust-num/num-iter][home].
+- [There is now a `std` feature][2], enabled by default, along with the implication
+  that building *without* this feature makes this a `#[no_std]` crate.
+  - There is no difference in the API at this time.
+
+**Contributors**: @cuviper
+
+[home]: https://github.com/rust-num/num-iter
+[num-356]: https://github.com/rust-num/num/pull/356
+[2]: https://github.com/rust-num/num-iter/pull/2
+
+
+# Prior releases
+
+No prior release notes were kept.  Thanks all the same to the many
+contributors that have made this crate what it is!
+