On Sun, Oct 14, 2012 at 10:20 AM, John Mija jon...@proinbox.com wrote:
This email is related to one sent to the Go mailing list[1] about the
great difference in compiling time between Rust which took 50 minutes,
and Go with a time of 2 minutes in build compiler, all libraries, all
commands and
On 2012-10-14, at 19:48 , Yiannis Tsiouris wrote:
Hi,
The build includes not only all of LLVM, but Clang as well.
Sorry if this is something obvious, but why is clang *needed* for Rust?
Without looking into the makefiles (so this really is nothing more than
a guess): rust calls llvm's
On Sun, Oct 14, 2012 at 12:11 PM, Masklinn maskl...@masklinn.net wrote:
On 2012-10-14, at 19:48 , Yiannis Tsiouris wrote:
Hi,
The build includes not only all of LLVM, but Clang as well.
Sorry if this is something obvious, but why is clang *needed* for Rust?
Without looking into the
On 10/14/12 10:20 AM, John Mija wrote:
This email is related to one sent to the Go mailing list[1] about the
great difference in compiling time between Rust which took 50 minutes,
and Go with a time of 2 minutes in build compiler, all libraries, all
commands and testing.
It looks that it is
On 2012-10-14, at 21:16 , Patrick Walton wrote:
* Rust builds itself three times for bootstrapping. This is unavoidable as
long as Rust is bootstrapped.
Aren't the second and third builds for sanity-checking purpose? Surely
if (when) Rust is mature and distributed as a tarball for
For those folks we might as well distribute only the binaries. Zero
build time. :D
Kevin
On Sun, Oct 14, 2012 at 12:32 PM, Masklinn maskl...@masklinn.net wrote:
On 2012-10-14, at 21:16 , Patrick Walton wrote:
* Rust builds itself three times for bootstrapping. This is unavoidable as
long
Regardless of all that, yes, the Rust compiler *is* slower than the Go
compiler. Not a factor 25, when you make a fair comparison, but still
quite a lot slower.
This has two reasons. Firstly, the Go language has partially been
designed with compiler speed in mind. It is a simple language,
What Brian wrote looks
about right to me. I don't think any of the deriving ideas we had
discussed could accommodate that particular example, though clearly it's
not hard to imagine how one might do so. Or perhaps use a macro.
Niko
Brian Anderson
October 13, 2012
2:57