Daniel Silverstone

Of course, as was suggested above, thinking carefully about whether or not this would be acceptable to add is also important. We'd be adding public API to the primary interface...

@rust-lang/infra could one of you move this issue as per @ehuss 's comment above?

Looks like we should close this off, thank you @cjwatson and @seanmonstar for your efforts.

Thank you for that thorough response.

I got very stuck when trying to work out how to update svd2rust to deal with registers which contained write-to-toggle bits (the stm32f103 and similar devices have, in their USB...

@mvirkkunen That sounds awesome. Once you have something you feel works nicely with current nightly and perhaps on the Blue Pill (stm32f103cbt6 IIRC) then I'd be pleased to give it...

I agree that a more general solution is better. There's a number of possible approaches here. The approaches outlined so far are good, an alternative is a more explicit approach....

So CI *could* run `rustup trust` or whatever as part of the pathway, providing that there's trust in who can cause CI to run then that should be okay. If...

@lnicola True, though there's an argument that any such toolchain should _probably_ have its channel file yanked from static.rust-lang.org no?

In that case we probably need a toolchain status file on static.rlo which rustup can read to understand if there are toolchains with security problems and/or known major regressions. Then...