@jarkko I used to be of the same opinion about standardization until this article: https://blog.m-ou.se/rust-standard/
@jarkko up to you what you want to do. But you're confusing between specification and standard.
@jarkko why is it critical to have gccrs have features in par with rustc
@jarkko would you not rather have the inconvenience of another toolchain (portability concerns aside), than wait for however long it will take to get gccrs to be ready... rustc is not standing still, and gccrs is far from having enough people to get it anywhere close
@jarkko you mentioned gccrs should reach feature parity with rustc before Rust being enabled by default in Linux would be an ok thing
@jarkko you do not like having to have 2 toolchains to compile the kernel, meaning you do not see it as an ok thing
@jarkko lack of a specification/standard is far from what stops any alternative Rust implementation (like gccrs) from reaching feature parity with rustc... there is enough tests and documentation to get close enough to the behavior of rustc, before that lack matters more than the effort to get that close