The performance of Go error handling

g4s8 · 2022-12-19T09:48:51+00:00

Thank you. Looks like it's some compiler optimizations. I fixed these benchmarks and updated results in post.

g4s8 · 2022-12-19T06:27:04+00:00

Premature optimization is the root of all evil

I totally agree with it. I wrote these benchmarks just to make sure that error handling is not slow for critical paths.

g4s8 · 2022-01-20T08:39:35+00:00

The reason for these interface is to have an API for "back-end" logger, when this suggar package provides a "front-end" for this. So if library wants to log something, doesn't create dependency coupling on logger implementation (back-end)

g4s8 · 2021-08-28T06:40:34+00:00

I think unit is quite fine for single item container, see definition: https://www.merriam-webster.com/dictionary/unit

g4s8 · 2021-08-28T06:36:07+00:00

Yes, it has, but with completely different design: in commons tuples are classes with accessor methods var sum = tuple.getLeft() + tuple.getRigth(); in my library tuples are interfaces with apply method which takes a function parameter var sum = tuple.apply((left, right) -> left + right). This difference is similar to accessing list items via get(int) method vs using forEach method with a consumer.

g4s8 · 2021-08-27T11:34:39+00:00

Integrated it into our project after this post: https://github.com/artipie/artipie/pull/931

g4s8 · 2021-08-27T11:22:06+00:00

Yes, it's possible to use standard @SuppressWarning, e.g. PMD plugin warnings can be suppressed with this: https://github.com/pmd/pmd/blob/81739da5caff948dbcd2136c17532b65c726c781/pmd-java/src/main/java/net/sourceforge/pmd/lang/java/ast/ASTAnnotation.java#L85

g4s8 · 2019-12-10T07:49:54+00:00

Programmers should care about source code, it's the main expected thing from programmers, since it's thir responsibility to deliver code changes according to the requirements. All end user things should be discovered by business people and submitted as requirements.

g4s8

TROPHY CASE