From 5ea63887c6fb85ec70111a19935fc48b62cc89f1 Mon Sep 17 00:00:00 2001
From: Tony Arcieri <bascule@gmail.com>
Date: Thu, 28 Dec 2023 08:33:27 -0700
Subject: [PATCH] Remove docs about `const_eval_limit`

It has been removed in recent Rust releases, and replaced with a printed
warning:

https://github.com/rust-lang/rust/pull/103877
---
 src/lib.rs | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/src/lib.rs b/src/lib.rs
index 569f5f59..0890712f 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -56,15 +56,6 @@
 //! pub const MODULUS_SHR1: U256 = MODULUS.shr(1);
 //! ```
 //!
-//! Note that large constant computations may accidentally trigger a the `const_eval_limit` of the compiler.
-//! The current way to deal with this problem is to either simplify this computation,
-//! or increase the compiler's limit (currently a nightly feature).
-//! One can completely remove the compiler's limit using:
-//! ```ignore
-//! #![feature(const_eval_limit)]
-//! #![const_eval_limit = "0"]
-//! ```
-//!
 //! ### Trait-based usage
 //!
 //! The [`Uint`] type itself does not implement the standard arithmetic traits