numeric range membership and len() are inconsistent with iteration for float steps
numeric range membership and len() are inconsistent with iteration for float steps: a task in repo2rlenv-swe-next (Harbor dataset). When using numeric range with a float step that has no exact binary representation (like 0.1 ), items produced by iterating the range are not recognized as members of…
The task
When using `numeric_range` with a float step that has no exact binary representation (like `0.1`), items produced by iterating the range are not recognized as members of the range by `in`, `index()`, or `count()`. Additionally, `len()` can disagree with the actual number of items iteration produces.
Part of FineEnvs/repo2rlenv-swe-next.