P99 CONF: Rust Is Safe. But Is It Fast?

แชร์
ฝัง
  • เผยแพร่เมื่อ 6 พ.ย. 2024

ความคิดเห็น • 7

  • @tylerbloom4830
    @tylerbloom4830 2 ปีที่แล้ว +2

    A very important mistake at 3:39: A circular reference such as "A holds a reference to one of B's fields, and B holds a reference to one of A's fields" does NOT cause a memory leak. Both will just have the same lifetimes and must be dropped at the same time (which the compiler will do for you).

  •  28 วันที่ผ่านมา

    The description of Rust in this talk contains some misconceptions. A 'static lifetime doesn't mean that the reference lives for the whole program execution (see e.g. Box::leak), just that the memory being pointed to cannot move or be dropped from the moment such a reference is created.

  • @nano8640
    @nano8640 3 ปีที่แล้ว +9

    i feel like a better title for this talk would be "Async rust is thread safe, but is it fast?" as this is not about the speed of rust generally : )

  • @agma
    @agma 3 ปีที่แล้ว

    Great talk! The only thing that's missing here is a performance comparison for a similar task implemented in, say, C++ and Go

  • @bjugdbjk
    @bjugdbjk 2 ปีที่แล้ว

    Excellent talk Glauber, You r explanation is so crisp and it's to the point !!

  • @cthutu
    @cthutu 2 ปีที่แล้ว

    I would say Rust is a more powerful C++. Traits is better than OOP/concepts, ownership/borrowing protects us, decent async model, hygienic macros (vs templates?), fat pointers and a vastly better type system just to think of some stuff off the top of my head. I am not sure why he is saying this.

  • @michapiotrowski5196
    @michapiotrowski5196 3 ปีที่แล้ว

    Thank you for this presentation.