From 3383204b3b6400667439867763d3e14f4d85c73a Mon Sep 17 00:00:00 2001
From: Nitin Kumar <59679977+lazysegtree@users.noreply.github.com>
Date: Mon, 2 Feb 2026 13:09:34 +0530
Subject: [PATCH] docs: Clarify the usage of options with implicit values

---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index df5d470..8f22186 100644
--- a/README.md
+++ b/README.md
@@ -189,6 +189,8 @@ If an option had both, then not specifying it would give the value `"value"`,
 writing it on the command line as `--option` would give the value `"implicit"`,
 and writing `--option=another` would give it the value `"another"`.
 
+Note that if `option` has implicit value, specifying `--option another` will not work. You must use `=` syntax - `--option=another` or `-o=another`(assumming `o` is a short name for the option). This is because no argument is required. Hence, there is no good way to determine if the next string is an argument to your option or a positional argument.
+
 Note that the default and implicit value is always stored as a string,
 regardless of the type that you want to store it in. It will be parsed as
 though it was given on the command line.