NightStrike via Gcc <[email protected]> writes: > On Mon, Nov 10, 2025 at 8:04 PM Arthur Cohen <[email protected]> > wrote: >> >> Hi everyone, >> >> We recently had a chat with Richi about what the Rust front-end could do >> to increase the interactions with the GCC side of our community. Richi >> pointed out that it would be good for patches to show up on the mailing >> list as they are merged in our development repository, rather than in >> batches whenever we send a patchset upstream. >> > [...] >> If anyone has anything else they'd like to see us do, please let me >> know! We are happy to work on anything that will increase the >> communication and/or interaction between the Rust side and the GCC side >> of our little front-end. > > https://gcc.gnu.org/pipermail/gcc-patches/2025-October/699320.html
I see that as orthogonal to this. The forge is also still in an experimental state but work is ongoing to get out of that (lots of discussion at Cauldron). If/when it is out of an experimental state, it may still not make sense for gccrs to move entirely there (though it may have a presence there). We don't currently have many CI runners available on the forge either. I don't think putting a new pipeline together (i.e. some new github actions glue) really translates into the same amount of effort as moving to a new hosting location, especially when that hosting location isn't fully ready to take on projects for the long-term yet. I think we should support them in spending as much time as possible in working on getting the implementation ready to build the stdlib and while small practical requests should be made to them, I don't consider this one of those.
