Live data from Hacker News

Viewing profile — mkirchner

mkirchner

HN member
Joined
Sun, Oct 15, 2017, 9:15 AM UTC
HN karma
601
Public activity
18 items

About mkirchner

No profile information was provided.

Recent public activity

  1. story
  2. story
  3. story
  4. comment
    Comment #37805549

    Ha! This was probably the first serious problem I ever tackled with an open source contribution! The year was 2002, the 2.4 Linux kernel had just been released and I was making mon…

  5. story
  6. comment
    Comment #36687188

    Beautiful, thanks!

  7. comment
    Comment #36687072

    #1 doing it in many 20-30min batches with little kids #2 see #1 Jokes aside, IMHO there was not a single challenge standing out in terms of implementation; getting the pieces to wo…

  8. comment
    Comment #36686961

    Agree. I was trying to mostly mimick the libavl API, hence the design decision.

  9. comment
    Comment #36686950

    Thanks! Yes, basically log_64(n) vs. log_32(n) and it would also require to switch to a 64 bit hash function and adjust hash exhaustion and bit fiddling arithmetic accordingly. Re …

  10. comment
    Comment #36686880

    Thank you, happy to share. These are excellent pointers. Regarding the batch construction, it's not immediately clear to me how to implement sorting since the order is implicit thr…

  11. story
    Show HN: A hash array-mapped trie implementation in C

    Long-simmering side project that is finally ready to see the light. HAMTs are a cool persistent data structure and implementing one has been a lot of fun. Beyond the code, there is…

  12. comment
    Comment #32190026

    This. Roughly a year ago I got interested in efficient immutability for my write-from-scratch-in-C Lisp [0] and started to write a HAMT implementation in C [1], along with a (somew…

  13. comment
    Comment #25330099

    Author here. To add context that seems lost on some: this is a cleaned-up version of my own notes from when I tried to understand the technical detail behind what Linus called "goo…

  14. comment
    Comment #25326969

    Author here. Thanks for fixing the title, I should have seen that!

  15. story
  16. story
  17. story
  18. story