Little questions to help

[frederikhors]

Hi @bjorn3,

thanks as always for your AMAZING AMAZING AMAZING work!

Is there a way to know how much work is missing from this project to be considered stable?

What can he do - who knows how - to help you finish?

How can you "split" the remaining work into tasks?

[bjorn3]

Apart from unwinding support and full std::arch support (which I'm both working on) there are not really major things that are missing. Just a lot of small bugs and papercuts. Better debuginfo support is a nice to have, but not essential. Currently the biggest bugs are the bevy issues opened today as well as a couple of bugs reported by the new abi-cafe version for which I still need to open an issue.

[frederikhors]

So - to better understand - what separates us from a stable release are the 71 issues minus this? Or even less?

Can we create a milestone?

[bjorn3]

After exception support and full std::arch support exists and all major known bugs are resolved, I think it would be interesting to try a crater run. That may catch a fair bit of new issues. As for when cg_clif will land on the stable channel, I think the compiler team will have to decide what the conditions for that are.

By the way I forgot raw-dylib support as other major missing feature. I believe cg_clif is the only reason libstd doesn't yet use raw-dylib internally (with a couple of minor exceptions that are patched away when building with cg_clif)

[frederikhors]

Ok. How can we make clear these points? Milestones with only a few issues written (and updated in the future) by you like in this issue?

[frederikhors]

I cannot create milestones unfortunately.