Ekago is a useful Go packages toolkit that I wrote for myself and published for others. And this is the first toolkit that contains both of improved logging and error generating mechanisms which are strongly linked to each other. Honestly, this project has been started as "another one logging library", but now it's not only that.

The root of project does not provide any code. It's toolkit, remember? All subpackages that this package has been named starting with "eka" avoiding your package's names import conflicting and import renaming. A trifle, but nice.

"eka" has no sense. Almost. Anyway, stop reading this bored message and go deep into the main packages: ekalog and ekaerr. You will be impressed, I hope!

---

Each Ekago subpackage has its own readme file where you can meet with them face by face, read more and get an answers to "What? Why? How?".

I strongly recommend to start your tour with the

• ekaerr: a package of error management that you desire, and then go to
• ekalog: an intelligence logging package for everything and especially for ekaerr

It doesn't take a lot of time. See you!

---

And if you need a quick description about all other packages, see:

• ekadeath: When os.Exit(1) is not enough and you love destructors (and their calls)
• ekadanger: Wanna see what interface{} is? Maybe compare functions? Divide by zero?
• ekamath: Bored about math.Min(upperBound, math.Max(lowerBound, x))?
• ekatime: Adore unixtime? Want to extract daystart, dayend? What's about time.Now() with rough precision?
• ekatype: Oh, you need UUID? Predefined interfaces? SQL type that if NULL then JSON is null?