What problem does it solve?
This Skill helps engineers choose and apply the right samber/lo package for collection transforms, concurrency, and lazy iteration in Go without guessing between immutable, mutable, parallel, or experimental options.
Core Features & Use Cases
- Core transforms: Use lo for map, filter, reduce, group, chunk, flatten, and error-aware variants across slices, maps, channels, strings, tuples, and numbers.
- Performance choices: Switch to lop for CPU-bound parallel work, lom for measured in-place optimization, loi for Go 1.23+ lazy pipelines, and simd only when benchmarking justifies it.
- Practical guidance: It explains stdlib interop, version constraints, immutability behavior, and when to avoid lo for I/O fan-out or infinite streaming pipelines.
- Use case: A developer can ask whether to use lo.Map, lop.Map, lom.Filter, or loi.Take for a specific dataset and get a safe, idiomatic recommendation.
Quick Start
Ask me to review your Go transformation task and recommend the correct samber/lo package, import path, and usage pattern for your data shape and Go version.