This is the #bootstrapping story of the language everybody talks about.
I don't like this. It's shameful.
This is what happens when you only look to one problem and don't care about anything else.
Discussion
Loading...
Oh there are more coming
@ekaitz_zarraga they zero-cost abstracted it so hard
@ekaitz_zarraga Wow, from 60 MB to 400 MB, quite an increase. I wonder right away if a compiler really has to be that large.
@wim_v12e From my point of view: no.
But I'm a simple man.
@wim_v12e And also not only that 60 -> 400MB increase, but also that it is cumulative!
For the 400MB to be built you need all the previous steps!
@ekaitz_zarraga And that is the only way to make it work on a new architecture? So if you don't have a lot of disk space and fast internet access, it's not possible. Not very inclusive.
@ekaitz_zarraga I hope this is just because it's the easiest path. There is surely a much shorter path available. They cannot create new features each release and start using them immediately? And have no stages/core or similar? ... it's not like Rust have the fastest compile times around either ;)
@simendsjo AFAIK they write the next compiler using features of the last one. That's the only guarantee they give from the bootstrapping perspective.
I might be wrong though.
@ekaitz_zarraga I was more thinking along the lines that the compiler was sticking to a small subset of the features rather than using the full language to avoid having this kind of bootstrapping.
@simendsjo That would be the sanest approach :)
@ekaitz_zarraga Wait what? Is this what I thing it is?
Every version must be compiled by the previous one?