kirk shoop

@kirkshoop

Developer. Worked on the Dash.js media player and some C++ libraries, such as rxcpp. All opinions courtesy of me alone.

Vrijeme pridruživanja: rujan 2012.

Tweetovi

Blokirali ste korisnika/cu @kirkshoop

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @kirkshoop

  1. proslijedio/la je Tweet
    prije 22 sata
    Odgovor korisnicima

    Say hello to struct Evil by

    Poništi
  2. prije 22 sata

    These same types of scheduling changes need to be made at coarser granularity as well. Algorithms that alter buffering and batching in async expressions will be used to achieve similar results.

    Poništi
  3. proslijedio/la je Tweet
    1. velj

    It's not every day that a read-after-write makes a server spend 4% of its CPU cycles in one instruction. Wrote that one up here:

    Poništi
  4. proslijedio/la je Tweet
    2. velj

    F's been showing it to computer science collegues at work who are fascinated. Knitting is basically a type of coding. I really love the way craft, stitch and colour can become data collection.

    Prikaži ovu nit
    Poništi
  5. proslijedio/la je Tweet
    1. velj

    Should be fun. And ranty. But mostly fun. :D

    Poništi
  6. proslijedio/la je Tweet

    Beautiful talk by David Jaz Myers, and very apropos to my own work. A general definition of open dynamical system

    Poništi
  7. proslijedio/la je Tweet
    1. velj

    A third recording of my Better Algorithm Intuition given at is online (first two were from and ) This one is 45 min longer and includes a lot more interactive Q&A 🙂

    Poništi
  8. proslijedio/la je Tweet
    30. sij
    Poništi
  9. proslijedio/la je Tweet
    1. velj
    Poništi
  10. proslijedio/la je Tweet
    31. sij
    Odgovor korisniku/ci

    I toyed with a new C-like language that supports the "try/catch" mechanism simply by passing in a second Return Address for the fail case so that when a failable function fails, it will return to the catch block of its caller without the need for the caller to check return value.

    Poništi
  11. proslijedio/la je Tweet
    31. sij

    A Universal I/O Abstraction for C++ New blog post about executors, asynchronous I/O, io_uring, coroutines and more ! ➡️ ⬅️

    Poništi
  12. proslijedio/la je Tweet
    31. sij

    While I cannot stop myself from having strong opinions about everything, I should thanks and who taught me quite a bit about their work on sender receivers! I hope I did a a good job explaining all of that.

    Prikaži ovu nit
    Poništi
  13. proslijedio/la je Tweet

    i believe i just did something no one has ever done before: i wrote a constant-time galois field implementation on a 6502 chipset, which not only does not have a constant-time hardware multiply instruction, but does not have a multiply instruction at all

    Prikaži ovu nit
    Poništi
  14. proslijedio/la je Tweet
    29. sij

    Excerpt from an upcoming blog post because it bears repeating: C++ Coroutines do not imply asynchrony, let alone scheduling C++ Coroutines do not imply asynchrony, let alone scheduling [Chorus] 🎵C++ Coroutines do not imply asynchrony, let alone scheduling 🎵

    Poništi
  15. proslijedio/la je Tweet

    If you see a weird ad that you think bears investigating, take a screen shot and send it my way. If you have ideas for different ways to parse this data, I’d love to hear.

    Prikaži ovu nit
    Poništi
  16. proslijedio/la je Tweet
    28. sij
    Odgovor korisnicima

    It makes it possible for the STL to deliver a suite of generic async algorithms as it already does for generic sequence algorithms. TL;DR: I would expect something like `retry` to live in the Standard Library.

    Poništi
  17. proslijedio/la je Tweet
    28. sij
    Odgovor korisnicima

    The biggest reason to not use ~T() on the continuation to mean "the task has been cancelled" is because ~T() gets called for lots of reasons. Distinguishing those reasons requires state.

    Poništi
  18. proslijedio/la je Tweet
    28. sij

    If you're really wondering how to get started with RxJS, there's a really great book from that is well worth your read If it helps you, let Chris know!

    Poništi
  19. proslijedio/la je Tweet
    28. sij

    Here's an example of writing a generic async algorithm using sender/receiver from the latest Executors proposal (P0443R12) + the changes suggested in P2006. This algo retries an async operation until it succeeds or is cancelled. It was fun to write!

    Poništi
  20. proslijedio/la je Tweet
    26. sij

    Someone should give an "Async Algorithm Intuition" talk

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·