See #307 for details. This issue tracks the fix for the VBA implementation.
Contributor guide
Tech stack
None
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Knowledge of VBAFamiliarity with floating point precision
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
First, read the referenced issue #307 to understand the floating point precision problem in the VBA implementation. Then locate the VBA source files in the repository, likely in a 'vba' directory, and identify the specific code that needs adjustment. Check any existing comments or maintainer guidance in #307 or related issues. The fix likely involves rounding or decimal arithmetic to avoid precision errors.
Fix floating point precision for VBA · google/open-location-code#319 | Good First Issue
