News for hackers. Stuff that matters.
Re:Rustgo: Calling Rust from Go with near-zero overhead by ori_b on Tuesday August 15, 2017 @12:11PM (#15019500)
For the kind of numerical code here, it's not going to be significantly faster.
Re:Rustgo: Calling Rust from Go with near-zero overhead by bascule on Tuesday August 15, 2017 @01:23PM (#15020278)
curve25519-dalek is 3X faster than the equivalent Go code (i.e. in the stdlib, authored by agl).

This is for a few reasons:

Rust has support for 128-bit integers (i.e. u128) which allows for faster arithmetic when operating on what are effectively multi-u128 bignums in an elliptic curve library.

LLVM is generally more sophisticated about optimizations. It wasn't until recently that go had an SSA-based compiler, so its optimizer isn't nearly as sophisticated as LLVM's, which has been developed for many years now.

Re:Rustgo: Calling Rust from Go with near-zero overhead by pjmlp on Tuesday August 15, 2017 @03:28PM (#15021511)
There is also gccgo, taking advantage of GCC's backend.

There is some ongoing work into an LLVM based compiler for Go, and LLVM now has Go as official supported bindings.

Re:Rustgo: Calling Rust from Go with near-zero overhead by tptacek on Wednesday August 16, 2017 @10:17AM (#15027622)
Go can and should fix the integer problem here. George Tankersley had a whole talk at Crypto Village this year about what a nightmare it is to write competitively fast curve code in Go.
Re:Rustgo: Calling Rust from Go with near-zero overhead by fnord123 on Tuesday August 15, 2017 @01:32PM (#15020367)
My information may be out of date, but last time I poked through the Go compiler, it did no vectorization or anything equivalent to march=native. So there's plenty of opportunity for Rust to be faster.