github.com/dgraph-io/gqlparser/v2/gqlerror.ErrorPosf
third-partyThe 1823rd most-called third-party function by production calls. Called 338 times across 2 modules; 338 of those run outside tests and generated code.
All of github.com/dgraph-io/gqlparser/v2/gqlerror → Docs on pkg.go.dev ↗
- prod calls
- 338
- non-test, non-generated
- all calls
- 338
- total callsites
- modules
- 2
- distinct callers
- in loop
- 28%
- of prod calls
- in tests
- 0%
- 0 calls
- resolved
- 100%
- to a known target
resolution mix
How each call resolves
How each call was attributed. Only resolved kinds, where the target function is known, count toward the ranking. Interface dispatch and unresolved receivers are reported separately and never guessed. Read the taxonomy →
- Package function (by syntax)100%A package function in a module outside the crawl, keyed by import path.
who calls this
Notable callers
Production calls into ErrorPosf from notable Go projects. Open one on the map to see what else it hammers.
- Dgraph 169 50%
where it's called
Callsites in the wild
12 representative callsites of 338, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
- in loop
top callers
The modules that reach for it
The modules that call ErrorPosf most in this snapshot.
- github.com/dgraph-io/dgraph/v2416950%
- github.com/hypermodeinc/dgraph/v2416950%