Corrected feature status of Result::map_or_else

map_or_else is now correctly labelled unstable and points to the
tracking issue on rust-lang/rust

1 files changed, 1 insertions, 1 deletions

diff --git a/src/libcore/result.rs b/src/libcore/result.rs
index 0e10c41ece7..22a7cedc189 100644
--- a/src/libcore/result.rs
+++ b/src/libcore/result.rs
@@ -494,7 +494,7 @@ impl<T, E> Result<T, E> {
     /// assert_eq!(x.map_or_else(|e| k * 2, |v| v.len()), 42);
     /// ```
     #[inline]
-    #[stable(feature = "result_map_or_else", since = "1.30.0")]
+    #[unstable(feature = "result_map_or_else", issue = "53268")]
     pub fn map_or_else<U, M: FnOnce(T) -> U, F: FnOnce(E) -> U>(self, fallback: F, map: M) -> U {
         self.map(map).unwrap_or_else(fallback)
     }