yes, well, this is because the author of said code likely didn't read the docs
or do their due diligence of the relevant standards .. this is the problem with
docs, they're not enforced by the standard. your PR contradicts the existing
documentation, which becomes more clear when indeed you have read both standards
and the most helpful thing you can do is to explain this point as faithfully as
possible to nim users, or 2-3 years down the line we'll be having the same
discussion because now there will be a platform for which your docs _don't_
match the implementation .. and then it will be worse, because we'll then have
to argue about whether to ship a release that breaks something that the docs
"guarantee"