goctx alternatives and similar packages
Based on the "Utilities" category.
Alternatively, view goctx alternatives based on common mentions on social networks and blogs.
-
项目文档
🚀Vite+Vue3+Gin拥有AI辅助的基础开发平台,支持TS和JS混用。它集成了JWT鉴权、权限管理、动态路由、显隐可控组件、分页封装、多点登录拦截、资源权限、上传下载、代码生成器、表单生成器和可配置的导入导出等开发必备功能。 -
excelize
Go language library for reading and writing Microsoft Excel™ (XLAM / XLSM / XLSX / XLTM / XLTX) spreadsheets -
Kopia
Cross-platform backup tool for Windows, macOS & Linux with fast, incremental backups, client-side end-to-end encryption, compression and data deduplication. CLI and GUI included. -
goreporter
A Golang tool that does static analysis, unit testing, code review and generate code quality report. -
create-go-app
✨ A complete and self-contained solution for developers of any qualification to create a production-ready project with backend (Go), frontend (JavaScript, TypeScript) and deploy automation (Ansible, Docker) by running only one CLI command. -
EaseProbe
A simple, standalone, and lightweight tool that can do health/status checking, written in Go. -
filetype
Fast, dependency-free Go package to infer binary file types based on the magic numbers header signature -
boilr
:zap: boilerplate template manager that generates files or directories from template repositories -
beaver
💨 A real time messaging system to build a scalable in-app notifications, multiplayer games, chat apps in web and mobile apps. -
go-underscore
Helpfully Functional Go - A useful collection of Go utilities. Designed for programmer happiness.
CodeRabbit: AI Code Reviews for Developers
Do you think we are missing an alternative of goctx or a related project?
Popular Comparisons
README
goctx
Get your context value faster
How to use
Replace
v := ctx.Value(key)
With
v := goctx.Value(ctx, key)
Benchmark
There will be little difference when there is only 1~2 context.WithXXX
calls
With 5 context.WithXXX
calls
BenchmarkValue/5/non_parallel/std-8 | 35313684 | 34.2 ns/op |
BenchmarkValue/5/non_parallel/goctx-8 | 42801348 | 30.0 ns/op |
BenchmarkValue/5/non_parallel/pure_map-8 | 16655377 | 72.8 ns/op |
BenchmarkValue/5/parallel/std-8 | 168420460 | 7.09 ns/op |
BenchmarkValue/5/parallel/goctx-8 | 185695462 | 6.35 ns/op |
BenchmarkValue/5/parallel/pure_map-8 | 67944997 | 17.6 ns/op |
With 20 context.WithXXX
calls
BenchmarkValue/20/non_parallel/std-8 | 7137338 | 168 ns/op |
BenchmarkValue/20/non_parallel/goctx-8 | 14623730 | 81.4 ns/op |
BenchmarkValue/20/non_parallel/pure_map-8 | 5282458 | 235 ns/op |
BenchmarkValue/20/parallel/std-8 | 42826857 | 27.9 ns/op |
BenchmarkValue/20/parallel/goctx-8 | 79149823 | 15.1 ns/op |
BenchmarkValue/20/parallel/pure_map-8 | 22206717 | 53.8 ns/op |
As we can see from the benchmark test, the map implementation is slower than the
standard one, so it is not recommended to use RegisterValueFunc
to register a
context value function, unless you do not want to see nested stack with Value
method
call (That's also the reason why RegisterValueFunc
is kept even it is not fast)