Andy Walsh

@__andywalsh

Opinions my own. He/Him.

Austin, Texas
Vrijeme pridruživanja: siječanj 2012.

Tweetovi

Blokirali ste korisnika/cu @__andywalsh

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

  1. proslijedio/la je Tweet
    30. sij

    I don’t tweet often, I only have 12 followers, but today was my final chemo session and I want to tell everyone (well 12 people at least! 😉)

    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet
    23. sij

    "I did a line-for-line port of my eval library from Go to Rust, and right away it was 5x faster [...] I was able to boost performance 12000x" Wish could understand just half of this article on "How to write fast code" 👇

    Poništi
  3. proslijedio/la je Tweet

    This is the hardest I've ever known someone didn't watch the thing they were writing about

    Poništi
  4. proslijedio/la je Tweet
    23. sij

    Rust 2.0 proposal: we rename the Send trait to “Yeet”

    Prikaži ovu nit
    Poništi
  5. proslijedio/la je Tweet
    20. sij

    I wrote a post for the Stack Overflow blog: What is Rust and why is it so popular?

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

    Is there a lua to wasm compiler called waluigi yet? You’re welcome

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

    How To Write Fast Rust Code by Christopher Sebastian:

    Poništi
  8. proslijedio/la je Tweet
    20. sij
    Poništi
  9. proslijedio/la je Tweet
    20. sij

    There is a new post on the Writing an OS in Rust blog: It builds upon the previous post about heap allocation and explains how different kernel allocator types can be implemented from scratch.

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

    ⏲️ As of today, we have about eighteen years to go until the Y2038 problem occurs. But the Y2038 problem will be giving us headaches long, long before 2038 arrives. I'd like to tell you a story about this.

    Prikaži ovu nit
    Poništi
  11. proslijedio/la je Tweet
    20. sij

    actix-web will live on with new leadership:

    Prikaži ovu nit
    Poništi
  12. proslijedio/la je Tweet
    19. sij

    I’m pleased to present the flame-bait sequel to my previous blog post: “No, dynamic type systems are not inherently more open.” (Please send me your hatemail at your earliest convenience.)

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

    Look at that beautiful implementation 😍

    A CPU instruction encoder in Rust, made via a procedural macro that does bitwise pattern-matching and binding.
    Prikaži ovu nit
    Poništi
  14. proslijedio/la je Tweet
    15. sij

    Autonomous Rust Unikernels in Google Cloud by NanoVMs Inc.:

    Poništi
  15. proslijedio/la je Tweet

    TIL that `dbg!(x)` is not the same as `println!("{:?}", x)` because dbg! takes ownership of x, while println! implicitly borrows instead. The equivalent to the println! is actually `dbg!(&x)`

    Poništi
  16. proslijedio/la je Tweet
    15. sij
    Poništi
  17. proslijedio/la je Tweet
    8. sij

    Videos from Rust Belt Rust 2019 are now available! Thanks again to all our attendees, speakers, and sponsors!

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

    Are there particularly helpful articles or blog posts that folks have come across that teach borrowing and ownership in ? (In addition to the chapter in TRPL, of course)

    Poništi
  19. proslijedio/la je Tweet

    some new rust blogging: "a little polymorphism", a two-parter on how rust traits let you write really expressive code by extending built-in types

    Prikaži ovu nit
    Poništi
  20. proslijedio/la je Tweet
    6. sij
    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:

    ·