Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Lilian Anatolie Moraru
    @lilianmoraru
    That's not from Rust
    I think that's from Dropbox
    And who knows, that allocator might leak intentionally.
    Nvm, I've mistaken with something else

    Yes, using

    #![feature(alloc_system)]
    extern crate alloc_system;

    and Not Rust's allocator, it is leaking...

    But you basically intentionally asked for it to leak in that case
    Lilian Anatolie Moraru
    @lilianmoraru
    Btw, I have mistaken it with this one: https://github.com/dropbox/rust-alloc-no-stdlib
    LeonineKing1199
    @LeonineKing1199
    Oh, that's so interesting.
    All I did was use sudo apt-get install rustc
    I'm on Ubuntu 16.04
    Maybe it's my version of valgrind?
    I'm on 3.11 of that
    Lilian Anatolie Moraru
    @lilianmoraru
    @LeonineKing1199 I also use Valgrind 3.11(which is the newest version) and the way you install Rust does not change the behavior
    Although, the recommended way of installing and using Rust would be through rustup: https://www.rustup.rs/
    LeonineKing1199
    @LeonineKing1199
    Well, I'm thankful to know that I just have a borked build.
    If other people are reporting 0 allocations, that's a good thing.
    Alexander Chepurnoy
    @kushti
    Hi folks! What paper book on Rust can you recommend, if I went through the online book on Rust website, have written some simple programs following it and now want to go deeper?
    Thomas Koehler
    @Bastacyclop
    deeper like Rust internals or as a user ?
    Thomas Koehler
    @Bastacyclop
    I would say that once you've read the official book you will learn the most by practicing and looking at community's code, articles, ...
    https://this-week-in-rust.org/ is great to find interesting stuff
    Thomas Koehler
    @Bastacyclop
    I can't really help you for paper books
    Thomas Koehler
    @Bastacyclop
    there is a lot of stuff here too https://github.com/ctjhoa/rust-learning, but the link is on the official website so you probably know it.
    Bruno Filippone
    @bfil
    Anyone cares for a code review? I’ve just open sourced an event store I’ve built with Rust, here it is: https://github.com/bfil/exar-db
    It would be great to get some feedback from the community!
    Alexander Chepurnoy
    @kushti
    @Bastacyclop thanks for the tips! I actually missed rust-learning :(
    Ingvar Stepanyan
    @RReverser
    Is there any efficient way to implement WeakMaps in Rust? Well, technically it's not WeakMap because Rust doesn't have GC and thus "weak" doesn't make much sense, but what I'm interested in is a way to store extra information on objects with O(1) lookup, where HashMap is not really the best solution.
    Another way of looking into this would be "traits with data members".
    To elaborate a little bit more - I'm going to store information associated with nodes in a tree retrieved from an external crate, so just adding data members is not really an option (without forking that crate just for this purpose); recreating entire tree but with wrappers around each node also seems too expensive (and requires lots of code to handle all kinds of nodes).
    The only approach that seems to allow this so far is defining custom allocator which would reserve extra space on objects, but I'm not sure I want to go down that way and hope for a simpler solution.
    Benjamin Cordes
    @benjyz
    Hi. noob here. I'm trying to create a sqlite database
    let conn = Connection::open_in_memory().unwrap();
    the doc tells me I can open like this: open<P: AsRef<Path>>(path: P) -> Result<Connection>
    Benjamin Cordes
    @benjyz
    nice.. got it let conn = Connection::open(path).unwrap();
    Benjamin Cordes
    @benjyz
    how do I put off warnings in cargo?
    Thomas Koehler
    @Bastacyclop
    which warnings ?
    Benjamin Cordes
    @benjyz
    "function is never used: xyz, #[warn(dead_code)] on by default"
    e.g.
    Thomas Koehler
    @Bastacyclop
    FYI this comes from the rust compiler (rustc) which is called by cargo. You can use #[allow(dead_code)] in the code. This is called an attribute https://doc.rust-lang.org/book/attributes.html.
    Benjamin Cordes
    @benjyz
    thanks. equally I try to ignore other warnings with
    warning: unused import, #[warn(unused_imports)] on by default
    with this.. doesn't work
    "#![warn(unused_imports)]"
    Thomas Koehler
    @Bastacyclop
    #[warn(stuff)] means you want a warning
    #[allow(stuff)] means you don't want anything
    #[deny(stuff)] means you want an error
    wow
    Benjamin Cordes
    @benjyz
    cool
    Thomas Koehler
    @Bastacyclop
    Benjamin Cordes
    @benjyz
    more basic question: what is a crate?
    "The compilation model centers on artifacts called crates. "
    Thomas Koehler
    @Bastacyclop
    Have you read the Book ?
    Benjamin Cordes
    @benjyz
    notyet
    not yet