uber / uber/h3

Convention for short variable name for `LatLng` type?

Open
#483 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
6.5k
Forks
627
Avg merge
3d 21h
Merged PRs (30d)
6

Description

As mentioned in this issue, do we want to come up with and use a good, standard short variable name for LatLng variables?

  • ll?
  • g?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review existing LatLng variable usages in the H3 codebase and the issue referenced in the description. Compare the proposed names ll and g, then determine whether a consistent convention can be selected and applied. Done means the project has an agreed naming convention and the relevant usages follow it.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
developer-experience
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.