Persona: You are a Go engineer who prefers declarative collection transforms over manual loops. You reach for lo to eliminate boilerplate, but you know when the stdlib is enough and when to upgrade to lop, lom, or loi.
samber/lo — Functional Utilities for Go
Lodash-inspired, generics-first utility library with 500+ type-safe helpers for slices, maps, strings, math, channels, tuples, and concurrency. Zero external dependencies. Immutable by default.
Official Resources:
This skill is not exhaustive. Please refer to library documentation and code examples for more informations. Context7 can help as a discoverability platform.
Why samber/lo
Go's stdlib slices and maps packages cover ~10 basic helpers (sort, contains, keys). Everything else — Map, Filter, Reduce, GroupBy, Chunk, Flatten, Zip — requires manual for-loops. lo fills this gap:
- Type-safe generics — no
interface{} casts, no reflection, compile-time checking, no interface boxing overhead
- Immutable by default — returns new collections, safe for concurrent reads, easier to reason about
- Composable — functions take and return slices/maps, so they chain without wrapper types
- Zero dependencies — only Go stdlib, no transitive dependency risk
- Progressive complexity — start with
lo, upgrade to lop/lom/loi only when profiling demands it
- Error variants — most functions have
Err suffixes (MapErr, FilterErr, ReduceErr) that stop on first error
Installation
go get github.com/samber/lo
| Package |
Import |
Alias |
Go version |
| Core (immutable) |
github.com/samber/lo |
lo |
1.18+ |
| Parallel |
github.com/samber/lo/parallel |
lop |
1.18+ |
| Mutable |
github.com/samber/lo/mutable |
lom |
1.18+ |
| Iterator |
github.com/samber/lo/it |
loi |
1.23+ |
| SIMD (experimental) |
github.com/samber/lo/exp/simd |
— |
1.25+ (amd64 only) |
Choose the Right Package
Start with lo. Move to other packages only when profiling shows a bottleneck or when lazy evaluation is explicitly needed.
| Package |
Use when |
Trade-off |
lo |
Default for all transforms |
Allocates new collections (safe, predictable) |
lop |
CPU-bound work on large datasets (1000+ items) |
Goroutine overhead; not for I/O or small slices |
lom |
Hot path confirmed by pprof -alloc_objects |
Mutates input — caller must understand side effects |
loi |
Large datasets with chained transforms (Go 1.23+) |
Lazy evaluation saves memory but adds iterator complexity |
simd |
Numeric bulk ops after benchmarking (experimental) |
Unstable API, may break between versions |
Key rules:
lop is for CPU parallelism, not I/O concurrency — for I/O fan-out, use errgroup instead
lom breaks immutability — only use when allocation pressure is measured, never assumed
loi eliminates intermediate allocations in chains like Map → Filter → Take by evaluating lazily
- For reactive/streaming pipelines over infinite event streams, → see
samber/cc-skills-golang@golang-samber-ro skill + samber/ro package
For detailed package comparison and decision flowchart, see Package Guide.
Core Patterns
Transform a slice
// ✓ lo — declarative, type-safe
names := lo.Map(users, func(u User, _ int) string {
return u.Name
})
// ✗ Manual — boilerplate, error-prone
names := make([]string, 0, len(users))
for _, u := range users {
names = append(names, u.Name)
}
Filter + Reduce
total := lo.Reduce(
lo.Filter(orders, func(o Order, _ int) bool {
return o.Status == "paid"
}),
func(sum float64, o Order, _ int) float64 {
return sum + o.Amount
},
0,
)
GroupBy
byStatus := lo.GroupBy(tasks, func(t Task, _ int) string {
return t.Status
})
// map[string][]Task{"open": [...], "closed": [...]}
Error variant — stop on first error
results, err := lo.MapErr(urls, func(url string, _ int) (Response, error) {
return http.Get(url)
})
Common Mistakes
| Mistake |
Why it fails |
Fix |
Using lo.Contains when slices.Contains exists |
Unnecessary dependency for a stdlib-covered op |
Prefer slices.Contains, slices.Sort, maps.Keys since Go 1.21+ |
Using lop.Map on 10 items |
Goroutine creation overhead exceeds transform cost |
Use lo.Map — lop benefits start at ~1000+ items for CPU-bound work |
Assuming lo.Filter modifies the input |
lo is immutable by default — it returns a new slice |
Use lom.Filter if you explicitly need in-place mutation |
Using lo.Must in production code paths |
Must panics on error — fine in tests and init, dangerous in request handlers |
Use the non-Must variant and handle the error |
| Chaining many eager transforms on large data |
Each step allocates an intermediate slice |
Use loi (lazy iterators) to avoid intermediate allocations |
Best Practices
- Prefer stdlib when available —
slices.Contains, slices.Sort, maps.Keys carry no dependency. Use lo for transforms the stdlib doesn't offer (Map, Filter, Reduce, GroupBy, Chunk, Flatten)
- Compose lo functions — chain
lo.Filter → lo.Map → lo.GroupBy instead of writing nested loops. Each function is a building block
- Profile before optimizing — switch from
lo to lom/lop only after go tool pprof confirms allocation or CPU as the bottleneck
- Use error variants — prefer
lo.MapErr over lo.Map + manual error collection. Error variants stop early and propagate cleanly
- Use
lo.Must only in tests and init — in production, handle errors explicitly
Quick Reference
| Function |
What it does |
lo.Map |
Transform each element |
lo.Filter / lo.Reject |
Keep / remove elements matching predicate |
lo.Reduce |
Fold elements into a single value |
lo.ForEach |
Side-effect iteration |
lo.GroupBy |
Group elements by key |
lo.Chunk |
Split into fixed-size batches |
lo.Flatten |
Flatten nested slices one level |
lo.Uniq / lo.UniqBy |
Remove duplicates |
lo.Find / lo.FindOrElse |
First match or default |
lo.Contains / lo.Every / lo.Some |
Membership tests |
lo.Keys / lo.Values |
Extract map keys or values |
lo.PickBy / lo.OmitBy |
Filter map entries |
lo.Zip2 / lo.Unzip2 |
Pair/unpair two slices |
lo.Range / lo.RangeFrom |
Generate number sequences |
lo.Ternary / lo.If |
Inline conditionals |
lo.ToPtr / lo.FromPtr |
Pointer helpers |
lo.Must / lo.Try |
Panic-on-error / recover-as-bool |
lo.Async / lo.Attempt |
Async execution / retry with backoff |
lo.Debounce / lo.Throttle |
Rate limiting |
lo.ChannelDispatcher |
Fan-out to multiple channels |
For the complete function catalog (300+ functions), see API Reference.
For composition patterns, stdlib interop, and iterator pipelines, see Advanced Patterns.
If you encounter a bug or unexpected behavior in samber/lo, open an issue at github.com/samber/lo/issues.
Cross-References
- → See
samber/cc-skills-golang@golang-samber-ro skill for reactive/streaming pipelines over infinite event streams (samber/ro package)
- → See
samber/cc-skills-golang@golang-samber-mo skill for monadic types (Option, Result, Either) that compose with lo transforms
- → See
samber/cc-skills-golang@golang-data-structures skill for choosing the right underlying data structure
- → See
samber/cc-skills-golang@golang-performance skill for profiling methodology before switching to lom/lop
1---2name: golang-samber-lo3description: "Functional programming helpers for Golang using samber/lo — 500+ type-safe generic functions for slices, maps, channels, strings, math, tuples, and concurrency (Map, Filter, Reduce, GroupBy, Chunk, Flatten, Find, Uniq, etc.). Core immutable package (lo), concurrent variants (lo/parallel aka lop), in-place mutations (lo/mutable aka lom), lazy iterators (lo/it aka loi for Go 1.23+), and experimental SIMD (lo/exp/simd). Apply when using or adopting samber/lo, when the codebase imports github.com/samber/lo, or when implementing functional-style data transformations in Go. Not for streaming pipelines (→ See golang-samber-ro skill)."4user-invocable: false5license: MIT6compatibility: Designed for Claude Code or similar AI coding agents, and for projects using Golang.7metadata:8 source: https://skillmd.com/skills/harmeet10000/golang-samber-lo9 author: samber10 version: "1.0.1"11 openclaw:12 emoji: "🧰"13 homepage: https://github.com/samber/cc-skills-golang14 requires:15 bins:16 - go17 install: []18allowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) mcp__context7__resolve-library-id mcp__context7__query-docs19---2021**Persona:** You are a Go engineer who prefers declarative collection transforms over manual loops. You reach for `lo` to eliminate boilerplate, but you know when the stdlib is enough and when to upgrade to `lop`, `lom`, or `loi`.2223# samber/lo — Functional Utilities for Go2425Lodash-inspired, generics-first utility library with 500+ type-safe helpers for slices, maps, strings, math, channels, tuples, and concurrency. Zero external dependencies. Immutable by default.2627**Official Resources:**2829- [github.com/samber/lo](https://github.com/samber/lo)30- [lo.samber.dev](https://lo.samber.dev)31- [pkg.go.dev/github.com/samber/lo](https://pkg.go.dev/github.com/samber/lo)3233This skill is not exhaustive. Please refer to library documentation and code examples for more informations. Context7 can help as a discoverability platform.3435## Why samber/lo3637Go's stdlib `slices` and `maps` packages cover ~10 basic helpers (sort, contains, keys). Everything else — Map, Filter, Reduce, GroupBy, Chunk, Flatten, Zip — requires manual for-loops. `lo` fills this gap:3839- **Type-safe generics** — no `interface{}` casts, no reflection, compile-time checking, no interface boxing overhead40- **Immutable by default** — returns new collections, safe for concurrent reads, easier to reason about41- **Composable** — functions take and return slices/maps, so they chain without wrapper types42- **Zero dependencies** — only Go stdlib, no transitive dependency risk43- **Progressive complexity** — start with `lo`, upgrade to `lop`/`lom`/`loi` only when profiling demands it44- **Error variants** — most functions have `Err` suffixes (`MapErr`, `FilterErr`, `ReduceErr`) that stop on first error4546## Installation4748```bash49go get github.com/samber/lo50```5152| Package | Import | Alias | Go version |53| --- | --- | --- | --- |54| Core (immutable) | `github.com/samber/lo` | `lo` | 1.18+ |55| Parallel | `github.com/samber/lo/parallel` | `lop` | 1.18+ |56| Mutable | `github.com/samber/lo/mutable` | `lom` | 1.18+ |57| Iterator | `github.com/samber/lo/it` | `loi` | 1.23+ |58| SIMD (experimental) | `github.com/samber/lo/exp/simd` | — | 1.25+ (amd64 only) |5960## Choose the Right Package6162Start with `lo`. Move to other packages only when profiling shows a bottleneck or when lazy evaluation is explicitly needed.6364| Package | Use when | Trade-off |65| --- | --- | --- |66| `lo` | Default for all transforms | Allocates new collections (safe, predictable) |67| `lop` | CPU-bound work on large datasets (1000+ items) | Goroutine overhead; not for I/O or small slices |68| `lom` | Hot path confirmed by `pprof -alloc_objects` | Mutates input — caller must understand side effects |69| `loi` | Large datasets with chained transforms (Go 1.23+) | Lazy evaluation saves memory but adds iterator complexity |70| `simd` | Numeric bulk ops after benchmarking (experimental) | Unstable API, may break between versions |7172**Key rules:**7374- `lop` is for CPU parallelism, not I/O concurrency — for I/O fan-out, use `errgroup` instead75- `lom` breaks immutability — only use when allocation pressure is measured, never assumed76- `loi` eliminates intermediate allocations in chains like `Map → Filter → Take` by evaluating lazily77- For reactive/streaming pipelines over infinite event streams, → see `samber/cc-skills-golang@golang-samber-ro` skill + `samber/ro` package7879For detailed package comparison and decision flowchart, see [Package Guide](./references/package-guide.md).8081## Core Patterns8283### Transform a slice8485```go86// ✓ lo — declarative, type-safe87names := lo.Map(users, func(u User, _ int) string {88 return u.Name89})9091// ✗ Manual — boilerplate, error-prone92names := make([]string, 0, len(users))93for _, u := range users {94 names = append(names, u.Name)95}96```9798### Filter + Reduce99100```go101total := lo.Reduce(102 lo.Filter(orders, func(o Order, _ int) bool {103 return o.Status == "paid"104 }),105 func(sum float64, o Order, _ int) float64 {106 return sum + o.Amount107 },108 0,109)110```111112### GroupBy113114```go115byStatus := lo.GroupBy(tasks, func(t Task, _ int) string {116 return t.Status117})118// map[string][]Task{"open": [...], "closed": [...]}119```120121### Error variant — stop on first error122123```go124results, err := lo.MapErr(urls, func(url string, _ int) (Response, error) {125 return http.Get(url)126})127```128129## Common Mistakes130131| Mistake | Why it fails | Fix |132| --- | --- | --- |133| Using `lo.Contains` when `slices.Contains` exists | Unnecessary dependency for a stdlib-covered op | Prefer `slices.Contains`, `slices.Sort`, `maps.Keys` since Go 1.21+ |134| Using `lop.Map` on 10 items | Goroutine creation overhead exceeds transform cost | Use `lo.Map` — `lop` benefits start at ~1000+ items for CPU-bound work |135| Assuming `lo.Filter` modifies the input | `lo` is immutable by default — it returns a new slice | Use `lom.Filter` if you explicitly need in-place mutation |136| Using `lo.Must` in production code paths | `Must` panics on error — fine in tests and init, dangerous in request handlers | Use the non-Must variant and handle the error |137| Chaining many eager transforms on large data | Each step allocates an intermediate slice | Use `loi` (lazy iterators) to avoid intermediate allocations |138139## Best Practices1401411. **Prefer stdlib when available** — `slices.Contains`, `slices.Sort`, `maps.Keys` carry no dependency. Use `lo` for transforms the stdlib doesn't offer (Map, Filter, Reduce, GroupBy, Chunk, Flatten)1422. **Compose lo functions** — chain `lo.Filter` → `lo.Map` → `lo.GroupBy` instead of writing nested loops. Each function is a building block1433. **Profile before optimizing** — switch from `lo` to `lom`/`lop` only after `go tool pprof` confirms allocation or CPU as the bottleneck1444. **Use error variants** — prefer `lo.MapErr` over `lo.Map` + manual error collection. Error variants stop early and propagate cleanly1455. **Use `lo.Must` only in tests and init** — in production, handle errors explicitly146147## Quick Reference148149| Function | What it does |150| --- | --- |151| `lo.Map` | Transform each element |152| `lo.Filter` / `lo.Reject` | Keep / remove elements matching predicate |153| `lo.Reduce` | Fold elements into a single value |154| `lo.ForEach` | Side-effect iteration |155| `lo.GroupBy` | Group elements by key |156| `lo.Chunk` | Split into fixed-size batches |157| `lo.Flatten` | Flatten nested slices one level |158| `lo.Uniq` / `lo.UniqBy` | Remove duplicates |159| `lo.Find` / `lo.FindOrElse` | First match or default |160| `lo.Contains` / `lo.Every` / `lo.Some` | Membership tests |161| `lo.Keys` / `lo.Values` | Extract map keys or values |162| `lo.PickBy` / `lo.OmitBy` | Filter map entries |163| `lo.Zip2` / `lo.Unzip2` | Pair/unpair two slices |164| `lo.Range` / `lo.RangeFrom` | Generate number sequences |165| `lo.Ternary` / `lo.If` | Inline conditionals |166| `lo.ToPtr` / `lo.FromPtr` | Pointer helpers |167| `lo.Must` / `lo.Try` | Panic-on-error / recover-as-bool |168| `lo.Async` / `lo.Attempt` | Async execution / retry with backoff |169| `lo.Debounce` / `lo.Throttle` | Rate limiting |170| `lo.ChannelDispatcher` | Fan-out to multiple channels |171172For the complete function catalog (300+ functions), see [API Reference](./references/api-reference.md).173174For composition patterns, stdlib interop, and iterator pipelines, see [Advanced Patterns](./references/advanced-patterns.md).175176If you encounter a bug or unexpected behavior in samber/lo, open an issue at [github.com/samber/lo/issues](https://github.com/samber/lo/issues).177178## Cross-References179180- → See `samber/cc-skills-golang@golang-samber-ro` skill for reactive/streaming pipelines over infinite event streams (`samber/ro` package)181- → See `samber/cc-skills-golang@golang-samber-mo` skill for monadic types (Option, Result, Either) that compose with lo transforms182- → See `samber/cc-skills-golang@golang-data-structures` skill for choosing the right underlying data structure183- → See `samber/cc-skills-golang@golang-performance` skill for profiling methodology before switching to `lom`/`lop`