From cbe2b0b4fe64fdbe7a398eeb689b0e75d12a2712 Mon Sep 17 00:00:00 2001
From: nanahi <130121847+na-na-hi@users.noreply.github.com>
Date: Mon, 20 Jan 2025 21:55:22 -0500
Subject: [PATCH] m_option: fix max/min range comment

The float type is now correctly clamped, so correct the
outdated comment.
---
 options/m_option.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/options/m_option.h b/options/m_option.h
index ed7fc641c2..d3f542c4af 100644
--- a/options/m_option.h
+++ b/options/m_option.h
@@ -398,9 +398,9 @@ struct m_option {
     // Most numeric types restrict the range to [min, max] if min<max (this
     // implies that if min/max are not set, the full range is used). In all
     // cases, the actual range is clamped to the type's native range.
-    // Float types use [DBL_MIN, DBL_MAX], though by setting min or max to
-    // -/+INFINITY, the range can be extended to INFINITY. (This part is buggy
-    // for "float".)
+    // Float type uses [FLT_MIN, FLT_MAX], and double type uses
+    // [DBL_MIN, DBL_MAX], though by setting min or max to -/+INFINITY,
+    // the range can be extended to INFINITY.
     // Preferably use M_RANGE() to set these fields.
     double min, max;