Go bindings to Rust's regex engine

Re:Go bindings to Rust's regex engine by pcwalton on Monday May 02, 2016 @03:47PM (#11614900)

Some did (SPARK for example), but they sacrificed dynamic allocation (i.e. malloc). Rust's real innovation (in an industry sense) is safe dynamic allocation without GC.

[ Parent | on HN ]

Re:Go bindings to Rust's regex engine by pjmlp on Monday May 02, 2016 @03:54PM (#11614967)

And I wish it manages to succeed, if it wasn't for Rust, the C++ Core Guidelines wouldn't be a thing.

[ Parent | on HN ]

Re:Go bindings to Rust's regex engine by masklinn on Monday May 02, 2016 @03:59PM (#11615031)

> if it wasn't for Rust, the C++ Core Guidelines wouldn't be a thing

So in a way, Rust has already succeeded.

[ Parent | on HN ]

Re:Go bindings to Rust's regex engine by catnaroek on Monday May 02, 2016 @05:45PM (#11615944)

So, basically, the only thing that is ever dynamically allocated in SPARK is activation records? Sounds overly restrictive.

[ Parent | on HN ]

Re:Go bindings to Rust's regex engine by PeCaN on Tuesday May 03, 2016 @12:17AM (#11617879)

ATS has had this (via linear types like Rust) for a while, but it's a massive pain to use. Rust's main innovation is gluing together existing ideas with a powerful community backing.

[ Parent | on HN ]