Patrick Walton

@pcwalton

Research engineer at Mozilla

San Francisco, CA
Vrijeme pridruživanja: studeni 2009.

Tweetovi

Blokirali ste korisnika/cu @pcwalton

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

  1. prije 1 sat

    I'm really tired of conspiracy theories

    Poništi
  2. prije 11 sati

    Something obvious I realized last week: Buddy allocators are the 1-dimensional analogue of 2D quadtrees and 3D octrees.

    Poništi
  3. proslijedio/la je Tweet
    prije 12 sati

    One nice thing with Rust is that its std containers (strings, vecs, hashmaps) are very well thought out, not trivially made higher-performance, and let people get on with work. Every gameco in C++ has their own because std:: is a dumpsterfire.

    Prikaži ovu nit
    Poništi
  4. 2. velj

    (2) There’s no high-profile language design decision you can point to and say “aha, that was a mistake!” No header files, for example. The slowness comes from a lot of smaller things that have real benefits, such as the borrow check.

    Prikaži ovu nit
    Poništi
  5. 2. velj

    Rust compiler performance is hard to have meaningful discussions about because: (1) There’s no single part of the compiler which is slow. In fact the compiler is pretty well optimized.

    Prikaži ovu nit
    Poništi
  6. 31. sij

    Been pleasantly surprised at the amount of demand there is for fast vector graphics rendering in the browser. Time to get it done :)

    Poništi
  7. 31. sij

    For those asking for Swift witness tables/intensional type analysis: Rust used to have those, and generating all the virtual copy/get-align/etc functions for every type took like 30% of the compilation time as I recall. Monomorphization was a compilation time *win*.

    Poništi
  8. proslijedio/la je Tweet
    31. sij
    Odgovor korisnicima

    Maybe the real problem is that generics are actually bad

    Poništi
  9. 30. sij

    Random thought: It sure is nice that we went with typed generics in Rust instead of untyped templates like C++/D/Nim/etc, so that we can even *have* the monomorphization debate at all.

    Poništi
  10. 30. sij

    *I'm* actually OK with this as an opt-in compilation mode, at least for cold functions. But are the people complaining about compilation time OK with it?

    Prikaži ovu nit
    Poništi
  11. 30. sij

    I'm increasingly convinced that the interpreter solution is the only reasonable alternative for Rust.

    Prikaži ovu nit
    Poništi
  12. 30. sij

    Easy to say "monomorphization is awful and Rust should never have done it", harder to say "I want all generic functions to be compiled to bytecode and to embed a Rust interpreter in every binary".

    Prikaži ovu nit
    Poništi
  13. 29. sij

    Maybe "rewrite it in Rust" is annoying, but from my point of view "Rust doesn't prevent every bug ever, so you should just use C or C++" is much more annoying.

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

    At the very last minute, the Halo Wars 1 (Xbox 360) developers changed the custom std::vector container equivalent (likely used in thousands of places in the code) to do range checking on *all* operator[]'s. This shipped.

    Prikaži ovu nit
    Poništi
  15. 28. sij
    Prikaži ovu nit
    Poništi
  16. 28. sij

    Huge thanks to s3bk for porting Pathfinder to Web Assembly!

    Prikaži ovu nit
    Poništi
  17. 27. sij

    The trick, of course, is to do this without slowing down development. It's tough, but I think it's doable.

    Prikaži ovu nit
    Poništi
  18. 27. sij

    IMO, modularity should be a goal of every browser engine. You should be able to share code between browsers, and between browsers and other types of apps, without taking the entire engine as a monolith.

    Prikaži ovu nit
    Poništi
  19. 27. sij

    To a first approximation, in 2020 image codecs would parse and entropy decode in Rust, throw the resulting bits on GPU, and do everything else there.

    Poništi
  20. 27. sij

    We need Rust image codecs to be used everywhere, like, yesterday.

    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:

    ·