Any container is either
- safe for concurrent processing (short:
ccsafe) - or not.
Note: Not being safe for concurrent processing has been normal for a looong time.
Just: normal is not a good, meaningful name.
Neither is oldway - another discarded idea.
Thus: we came up with oneway - as there is only one way to use it safely: single threaded - not concurrent.
das- a Dictionary for Any String || lint |
dot- a tree of named anythings || lint
dotpath- a parser for user-provided strings to be understood as a (list of) path with special awareness of triple dots (to recourse) and of trailing double dots (to inspect) || lint
fs- a type safe alternative to direct use ofpath/filepath|| lint
fscache- a cache for file data for any*fs.FsFile|| lint
lru- a concurrency-safe LRU cache - as found in "golang.org\x\build\internal\lru" || lint
svp- a String Value Pair (aka Named Constant) || lint
tag- a Tag (= a String Value Pair (aka Named Constant)) || lint
tag/ami- a drop-in enhancement for atag: adding introspective methods fromdo/ami|| lint
tagmap- a Tag Map (= a dictionary of String Value Pair s (asmap) || lint
list- an extension of the standardcontainer/listpackage || lint
lsb- a Lazy String Buffer - a gem hidden inpath/path.go- chapeaux to Rob Pike || lint
sync- a drop-in replacement for standardsyncwith empty/no-op equivalents (used e.g. inoneway/lsm) || lint
drum- a simple beat-counterccsafe/drum|| lint
oneway/drum|| lint
lsm- a Lazy String Mapccsafe/lsm|| lint
oneway/lsm|| lint
stack- a simple stack for anything; not typesafe; just: it's pattern is used typesafe elsewhere. You may like to do same.ccsafe/stack|| lint
oneway/stack|| lint
Note: Some kinds may deserve to be implemented both ways, as the ccsafe version is usually less performant.
Note: Some kinds are safe for concurrent processing by construction. Notably immutable things.
Your suggestions, remarks, questions and/or contributions are welcome ;-)
Hey dude! Help me out for a couple of 🍻!
