gnoack

10 ms·

1. 61.▲
   by gnoack 7y ago

   I'm not sure what you mean by "nested function" as a cleanup mechanism, and couldn't find a mention of state machines for cleanup purposes either (but maybe I'm searching for the wrong keywords). Is there existing o
2. 62.▲
   by gnoack 7y ago

   Thanks for the pointer! I'm having trouble categorizing this one, tbh. (also its relationship to what dwohnitmok says on this HN discussion) Superficially, the code on this Wikipedia page looks like the bracket pattern in similar to th
3. 63.▲
   by gnoack 7y ago

   Admittedly the part about xUnit was a slight derail, but I felt it made some sense to mention, as an example for "the framework" invoking cleanup handlers for the developer. The remark about unnecessary tearDown() hooks is probabl
4. 64.▲
   The Setup-Cleanup Problem(blog.gnoack.org)

   48 points by gnoack 7y ago|26 comments
5. 65.▲
   by gnoack 7y ago

   AI, Blockchain, Quantum COK mputing... Bingo!
6. 66.▲
   by gnoack 7y ago

   The net/http library is the caller in this case, so that would be consistent with the rule that callers should start goroutines. Request handlers are a bit of a special case too, in that they are a framework for dispatching tasks to be
7. 67.▲
   by gnoack 7y ago

   The Raspberry Pi handles the load well after fixing that configuration mistake. (I still need to investigate to understand in detail what went wrong there...)
8. 68.▲
   by gnoack 7y ago

   (whoops, excuse the bad webserver config... should be fixed now) > Don't require users of your API to start goroutines to use your API correctly. Actually, what I postulate in the article is different... The theory is that making th
9. 69.▲
   Goroutines and APIs(blog.gnoack.org)

   106 points by gnoack 7y ago|31 comments
10. 70.▲
    How to Review Code(blog.gnoack.org)

    2 points by gnoack 8y ago|0 comments
11. 71.▲
    by gnoack 8y ago

    I did the captcha, and the page greeted me with "an error occurred". Next click lead me back to the captcha step.
12. 72.▲
    Procedurally generated trees(blog.gnoack.org)

    2 points by gnoack 8y ago|0 comments
13. 73.▲
    by gnoack 8y ago

    Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn
14. 74.▲
    The harmful consequences of the robustness principle(tools.ietf.org)

    1 points by gnoack 8y ago|0 comments
15. 75.▲
    by gnoack 8y ago

    Arguably, in many of the listed languages, similarly easy to read code can be achieved through different means. For example, in Python, it's often simpler to just use keyword arguments, possibly with default parameter values: def m
16. 76.▲
    by gnoack 8y ago

    This is the ICU solution to it: http://userguide.icu-project.org/formatparse/messages
17. 77.▲
    by gnoack 8y ago

    The ICU project does that: http://userguide.icu-project.org/formatparse/messages
18. 78.▲
    Shared Base Fixture technique for unit tests(blog.gnoack.org)

    1 points by gnoack 8y ago|0 comments
19. 79.▲
    by gnoack 8y ago

    Thanks for the feedback. :) To clarify, in the context of the article, "making errors observable from the outside" is not meant at the per-function level, but meant at the level of the whole program, which includes abort(). I shou
20. 80.▲
    by gnoack 8y ago

    I've written an article on error handling some point and ended up with: "An error is when the program is operating outside the intended path of execution." What counts as intended is a question of definition, but in concrete
21. 81.▲
    No error left behind(blog.gnoack.org)

    1 points by gnoack 8y ago|0 comments