News for hackers. Stuff that matters.
Re:How to speed up the Rust compiler some more by stevedonovan on Wednesday November 23, 2016 @04:37AM (#13021326)
Here's some thinking outside the box. Traditional compilers are focused on building an executable as fast as possible, throwing away an enormous amount of state each time. The new rustc incremental compilation attempts to re-use some of that computed state, although still early days. If however the compiler's state remains persistent (it is running as a daemon) then small code changes should usually be pretty fast - it's analogous to the code scanners of Eclipse. If the target of the compiler isn't a native executable, but a continuously updated image containing code, then the link gets pretty fast as well. The result will not be fast, but it will be _fast enough_ to test changes.
Re:How to speed up the Rust compiler some more by barrkel on Wednesday November 23, 2016 @06:31AM (#13021787)
The Delphi compiler, when hosted in the IDE, has done this since 1996 or so.

The symbol table, generated code etc. for every compilation unit is kept in memory and only discarded if the source is modified. All imports across compilation units are done via a double indirection, so the symbols can be unlinked and relinked more easily.

(Sub-second recompiles in Delphi are the norm, not the exception. In large projects, most of the time during dev builds is linking, and that's usually only a few seconds.)

Re:How to speed up the Rust compiler some more by pjmlp on Wednesday November 23, 2016 @07:04AM (#13021963)
Which is why I kind of think that it is a bit sad when millennials think Go compilation speed is some kind of achievement.

Specially given Delphi features vs Go ones.

Re:How to speed up the Rust compiler some more by jerf on Wednesday November 23, 2016 @09:14AM (#13022744)
I've said a couple of times that new language designers should thank their lucky stars that C++ has set the bar for "fast compilation" so low. Coming out of the gate with a compiler that's "faster than C++!" is pretty doable even for a relatively compile-time heavy language. If you had to come out of the gate with something as fast as Delphi to be taken seriously, we wouldn't get very many new languages.

(I mention this in the context of my observation that the minimum bar to be taken seriously for a language is going steadily up. You certainly need a standard library that is powerful out of the gate, whether or not it is necessarily "part" of the language, and we're getting perilously close to the language being required to ship some heavy-duty HTTP stuff, possibly a server implemented in the language, before it stands a chance. Rust may have snuck in under the wire on that, though of course that stack is developing apace even so.)

Re:How to speed up the Rust compiler some more by stevedonovan on Wednesday November 23, 2016 @09:50AM (#13022988)
Go (despite its faults) definitely raised that minimum bar; a language needs to arrive with a package manager and doc tools, as well as enough standard library to get non-trivial things going. Rust made the right decision on HTTP - let the ecosystem provide. Of course, the result of that is summarized in the quote by Grace Hopper: “The wonderful thing about standards is that there are so many of them to choose from.”
Re:How to speed up the Rust compiler some more by marcosdumay on Wednesday November 23, 2016 @11:04AM (#13023502)
There's always the Python way:

Let the ecosystem provide, then, once there's a few clean winners, pick one as the official (while keeping the others there, obviously).

Re:How to speed up the Rust compiler some more by paulddraper on Wednesday November 23, 2016 @09:07PM (#13027458)
C++/Boost does that
Re:How to speed up the Rust compiler some more by marcosdumay on Thursday November 24, 2016 @06:56AM (#13029857)
Yes (what is quite inline with the C tradition).

What is interesting is that I can't think of a lot languages that do it. It should be the default, as it's easy, safe, and gets good results. Somehow, it isn't.

And then there's the Haskell's way of: let the community informally choose the one best option, and when somebody uses any of the other ones, just get somebody near him telling "nobody goes there anymore, come to this other place". It works very well, but is a bit confusing for newbies.

Re:How to speed up the Rust compiler some more by pjmlp on Wednesday November 23, 2016 @11:16AM (#13023605)
Go's minimum bar is well below Active Oberon, Delphi, Eiffel, Java and .NET ones.
Re:How to speed up the Rust compiler some more by jerf on Wednesday November 23, 2016 @02:49PM (#13025294)
Remember I'm not discussing what they have now, though; the question is what they came out of the gate with in their 1.0. I'm fairly confident Go 1.0 was much more useful than Java 1.0. Java 1.0 certainly didn't ship with a built-in web server and routing stack, or even anything close to that high-level functionality, even if it did ship with more data structures that Go has even now. .Net was a closer call, but, then, .Net came later, the bar had raised. Can't speak to the other ones but I would imagine their first releases were also less useful than Go.
Re:How to speed up the Rust compiler some more by pjmlp on Wednesday November 23, 2016 @03:56PM (#13025779)
> Java 1.0 certainly didn't ship with a built-in web server and routing stack

Kind of, it supported distributed computing via CORBA and RMI.

A built in web server was released as part of Java 6, 2006.

> Can't speak to the other ones but I would imagine their first releases were also less useful than Go.

The fact is that Go, released in 2009, was a pretty bare bones compared to the state of those programming languages in 2009.

Also while Go might had an HTTP package on version 1.0, it surely still doesn't have a GUI framework on 1.8, which those languages had on 1.0.

EDIT: Rephrased a bit the answer.

Re:How to speed up the Rust compiler some more by jerf on Wednesday November 23, 2016 @09:40PM (#13027588)
"A built in web server was released as part of Java 6, 2006."

Go isn't even that old yet. You're welcome to discuss what you like but I'm talking about what thing came with at first release.

"Also while Go might had an HTTP package on version 1.0, it surely still doesn't have a GUI framework on 1.8, which those languages had on 1.0."

Point. And even by 1.0 Java's was at least modestly capable by the standards of the time, as I recall. It didn't have everything, certainly couldn't compete with all the custom widgets you could buy for Windows, but usable.

Re:How to speed up the Rust compiler some more by pjmlp on Wednesday November 23, 2016 @11:30AM (#13023698)
I believe if Sun and MS had provided optimized AOT native compilers as part of Java and .NET, instead of waiting 20 years to do so or relying on third parties, C++ use cases would be even less than they are nowadays.

Just in cases someone mentions NGEN, it is just intended to enable fast startups.

Re:How to speed up the Rust compiler some more by neikos on Wednesday November 23, 2016 @09:40AM (#13022920)
python has a http server coming with the standard installation
Re:How to speed up the Rust compiler some more by adrianN on Wednesday November 23, 2016 @07:09AM (#13021986)
Especially given the CPUs used in the computers back when Delphi was popular.
Re:How to speed up the Rust compiler some more by pjmlp on Wednesday November 23, 2016 @07:50AM (#13022239)
Yeah that as well, and even Turbo Pascal was already quite fast on MS-DOS systems (I was using it with MS-DOS 5.0).
Re:How to speed up the Rust compiler some more by noir_lord on Wednesday November 23, 2016 @09:10AM (#13022711)
Delphi is still my favourite ever development environment even though I haven't touched it for over a decade.

IDE power, the VCL, amazing documentation, rapid builds, clean OO language, it had it all.

Re:How to speed up the Rust compiler some more by mickronome on Wednesday November 23, 2016 @10:04AM (#13023089)
For building GUI small/medium applications on windows I don't think there have never existed anything more convenient. Not to mention that usually your only deliverable was a single executable file.
Re:How to speed up the Rust compiler some more by noir_lord on Wednesday November 23, 2016 @10:45AM (#13023351)
Agreed and it was fast at runtime as well, not far off the same speed as C++ for a lot of things, I remember using it for some pretty performance intensive stuff and you could easily drop to assembly if needed.

It was a fantastic development environment even by modern standards but for its time it was well ahead of the curve.

I still try out Lazarus once in a while just for nostalgia :)

Re:How to speed up the Rust compiler some more by pjmlp on Wednesday November 23, 2016 @11:32AM (#13023712)
It IS fast.

We are doing a project with a company that uses it for all their Windows applications.

Delphi conferences are still a thing in Germany.

Re:How to speed up the Rust compiler some more by noir_lord on Wednesday November 23, 2016 @01:19PM (#13024521)
It was pretty big over here as well, the last version I used in anger was 7 but I still see the odd job posted for Delphi devs.
Re:How to speed up the Rust compiler some more by grokys on Wednesday November 23, 2016 @04:52AM (#13021394)
I think the Roslyn compiler does something similar to what you're suggesting.

http://www.dotnetcurry.com/csharp/1258/dotnet-platform-compi...

> Every time a developer changes a single character in any of the files, a new copy of all the data structures is created, leaving the previous version unchanged. This allows a high level of parallelism and concurrency in the Roslyn engine, as well as in its consumers, thereby preventing any race conditions to occur. Of course, in the interest of performance, these operations are highly optimized and reuse as much of the existing data structures as possible. Again, those being immutable makes this possible!

Re:How to speed up the Rust compiler some more by stevedonovan on Wednesday November 23, 2016 @05:15AM (#13021486)
Right! That's a compiler designed to be used as a service! Most compilers are usually in a terrible hurry to build that executable before people start playing with light sabers or thinking about new programming languages [1].

I first thought about this when working on UnderC, a hopelessly over-ambitious C++ interpreter. Functions could be recompiled, because there was an indirect reference to the actual code. And this is of course exactly how Lisp people used their compiler. (The 'image' reference of course is to Smalltalk)

[1] https://commandcenter.blogspot.co.za/2012/06/less-is-exponen...

Re:How to speed up the Rust compiler some more by pas on Wednesday November 23, 2016 @05:57AM (#13021636)
Scala's new compiler (dotty) also tries to go that way (first of all using streaming AST-s for better cache locality).

The problem is, that usually this "keep state and just percolate changes" is easier said than done. But we're getting there.

See also:

https://www.youtube.com/watch?v=TS1lpKBMkgg#t=23m38s (scalac performance) https://www.youtube.com/watch?v=TS1lpKBMkgg#t=37m53s (what do we really need from "computing science" to do programming)

https://d-d.me/talks/scalaworld2015/#/49

Re:How to speed up the Rust compiler some more by pjmlp on Wednesday November 23, 2016 @07:02AM (#13021949)
Besides the sibling comments, this is how Lisp, Smalltalk, Ada and Eiffel environments work.

Even C++ had such tools in the past via Energize C++ and VisualAge for C++ v.40.

Microsoft is now kind of following this path with /fastlink and improved database backend for code metadata.

EDIT: Typo

Re:How to speed up the Rust compiler some more by amelius on Wednesday November 23, 2016 @04:44AM (#13021357)
Yes, and it would be even nicer if such techniques would be available outside the compiler community. In fact, it could perhaps even be a language feature.
Re:How to speed up the Rust compiler some more by pjmlp on Wednesday November 23, 2016 @06:59AM (#13021938)
You mean like Lisp, Smalltalk?
Re:How to speed up the Rust compiler some more by adamrezich on Wednesday November 23, 2016 @09:11AM (#13022726)
Also that language Jonathan Blow is working on https://www.youtube.com/watch?v=HLk4eiGUic8
Re:How to speed up the Rust compiler some more by vanderZwan on Wednesday November 23, 2016 @08:21AM (#13022425)
The new kid on the Smalltalk block is Pharo:

http://pharo.org/

Re:How to speed up the Rust compiler some more by flukus on Wednesday November 23, 2016 @09:55PM (#13027656)
Traditional as in c? Object files would maintain state and build incrementally.