you are viewing a single comment's thread
view the rest of the comments
[–] 20 points 3 months ago (8 children)

Zig is not as strict as Rust for memory management

  • source
  • parent
  • hideshow 8 child comments
  • [–] 10 points 3 months ago (7 children)
  • [–] 7 points 3 months ago* (6 children)

    yes, but when you make a port from one language to another, usually you want to rewrite it as a translation first, then refactor later with the features that language provides. A port that refactors everything in the first release is too risky.

    The fact the translation has unsafe blocks only demonstrates the Zig version is not really safe as per Rust standards.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 5 points 3 months ago (5 children)

    my comment was just pointing out to unsafe rust blocks used in sloppy rewrite.

  • source
  • parent
  • hideshow 5 child comments
  • [–] -4 points 3 months ago (4 children)

    You clearly don't even know what unsafe in rust means. And it's not something you can avoid when FFI is involved, slopping involved or otherwise.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 3 points 3 months ago (2 children)
  • [–] -5 points 3 months ago (1 child)

    You can interface with a C++ JS engine without unsafe (which is equivalent to just using C btw), if you just really put a real effort into it.

    😇

    I do love me some internet gantry commentary. Especially when it's super confident and acting knowledgable, with multiple layers of genius on display.

  • source
  • parent
  • hideshow 1 child comment