FWIW, it does appear that at least for now, the project is targeting a version of Rust that is substantially behind the current stable version: > For some cont

FWIW, it does appear that at least for now, the project is targeting a version of Rust that is substantially behind the current stable version: > For some context, my current project plan brings us to November 2022 > where we (unexpected events permitting) should be able to support > valid Rust code targeting Rustc version ~1.40 and reuse libcore, (current stable rustc is 1.62, 1.40 is from Dec. 19, 2019) Which is in line with what you're saying about gcc likely being behind initially, of course. I bet it's easier to go from version 1.40 to 1.6x than from version nil to 1.40, though - you have to start somewhere, and the later you start, the longer till you have a viable alternative.