Instead of emitting one giant crate containing everything, we tweaked our SQL-to-Rust compiler to split the output into many smaller crates. Each one encapsulating just a portion of the logic, neatly depending on each other, with a single top-level main crate pulling them all in.

  • gressen@lemm.ee
    link
    fedilink
    arrow-up
    32
    ·
    edit-2
    1 month ago

    They changed the graphic already but holy AI on a stick! Now his arm is still behind the saw but his fingers are already gone. Lol

  • BB_C@programming.dev
    link
    fedilink
    arrow-up
    6
    ·
    1 month ago

    Cool and all. But missing some experiments:

    • cranelift
    • multi-threaded rustc
    • undoing type erasure after the split
    • lto = "off"
    • strip = false (for good measure)
    • [PRIORITY] a website that works with Tridactyl✋
  • FizzyOrange@programming.dev
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    1 month ago

    What’s the advantage of compiling to Rust here? Maybe it would be faster if they just skipped straight to LLVM.

  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    1 month ago

    Impressive improvement! But why did they choose Rust to compile on demand in the first place, if compile time was that important?

  • sga@lemmings.world
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    29 days ago

    i don’t really know how much could they optimise more, but they can predict it by fitting the number of cores with the amount of time taken, that is amdahl’s law.