Live data from Hacker News

Viewing profile — cafxx

cafxx

HN member
Joined
Sun, Aug 16, 2015, 11:10 AM UTC
HN karma
336
Public activity
144 items

About cafxx

No profile information was provided.

Recent public activity

  1. story
  2. comment
    Comment #46269120

    Filed a CL for this, hopefully it gets merged ~soon. https://go-review.googlesource.com/c/go/+/729920

  3. comment
    Comment #46259581

    That's not how it's implemented (it returns false if you're inside a Do() on a unsupported platform), although I agree the wording should be clearer.

  4. comment
    Comment #46259495

    I find this example mildly infuriating/amusing: func Encrypt(message []byte) ([]byte, error) { var ciphertext []byte var encErr error secret.Do(func() { // ... }) return ciphertext…

  5. comment
    Comment #46250702

    The point is that no-one is thinking to add knobs, or allow alternative GCs.

  6. comment
    Comment #46240149

    > GOGC was introduced in Go 1.5 yes, that's quite literally what I meant by "GOGC has always been there". 1.5 was released 10 years ago, just 3 years after 1.0. So to summarize: th…

  7. comment
    Comment #46237129

    Your previous message was referring to Go "getting" knobs, but GOGC has always been there. The older GC algorithm won't stay, IIRC the plan is for it to be removed in 1.27 (it's ke…

  8. comment
    Comment #46232054

    I still would be wary, even in that case. Go does not guarantee that the address of an allocation won't change over the lifetime of the allocation (although current implementations…

  9. comment
    Comment #46232001

    Not sure what you are referring to. There are no knobs involved in the things I mentioned (aside from the one to enable the experiment, but that's just temporary until the experime…

  10. comment
    Comment #46227177

    > If you really want an arena like behavior you could allocate a byte slice and use unsafe to cast it to literally any type. A word of caution. If you do this and then you store po…

  11. comment
    Comment #46227146

    There's a bunch of activity ongoing to make things better for memory allocation/collection in Go. GreenTeaGC is one that has already landed, but there are others like the RuntimeFr…

  12. comment
    Comment #39788005

    I think that the idea of not initiating writeback immediately derives mostly from the days of spinning rust, where read latencies would be noticeably impacted if you initiated writ…

  13. story
  14. story
    Show HN: Mgo: build a single Go binary optimized for all GOAMD64 variants

    mgo builds the same program once for each GOAMD64 variant, and then bundles all of them with a launcher that at runtime picks the correct one for the local system. Handy if you hav…

  15. comment
    Comment #38167608

    Would be nice also if they fixed the ubiquitous "network errors" that happen approximately every single time...

  16. comment
    Comment #37682836

    Not to be the devil's advocate here, but almost certainly it can be the case that data was used to define heuristics (potentially using automated statistical methods) that a engine…

  17. comment
    Comment #37492571

    ...or maybe Windows should just offer an API for marking a file for deletion once it's not in use anymore (I understand unlink semantics may not be possible, but that's not what my…

  18. comment
    Comment #37312528

    Or you could simply invoke a GC periodically (or every N times a key is removed from the map, or similar schemes). Another simple way, if we don't like the idea of triggering GCs m…

  19. comment
    Comment #37301267

    Why not just allocating the blobs off-heap? (That is something you probably want to do anyway if it's cryptographic material, to avoid being at the mercy of the GC leaving copies a…

  20. comment
    Comment #37139648

    'Oumuamua was closer to 8:1 https://en.wikipedia.org/wiki/%CA%BBOumuamua

  21. comment
    Comment #36491026

    In the example you linked it's comparing two threads reading from the same or separate cache lines, no? If so, that's not really the point I was referring to (as the two variables …

  22. comment
    Comment #36490498

    A point that AFAICT is not articulated in the article is why the two cached fields should be in their own dedicated cache line (e.g. why readIdxCached_ can not share the cache line…

  23. story
  24. comment
    Comment #36291596

    Yes, that's the whole point. I did not claim you can control every single module in the QR. I just said that you can get different QR codes for the same semantic content.

  25. comment
    Comment #36290671

    Yes, that's what I meant.