Move clean types into their own file#66984
Conversation
bbcf2a3 to
be17771
Compare
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
4f692d1 to
de35bb9
Compare
|
The job Click to expand the log.I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
de35bb9 to
12a2671
Compare
|
ping @kinnison |
|
@GuillaumeGomez Okay, I've been through the commit sequence and it looks clean to me. You can squash it down if you want, or else just let Bors know I approve. |
|
Let's keep the commit history as is then, I kinda like the history flow as it is. :) @bors: r=kinnison |
|
📌 Commit 12a2671 has been approved by |
…kinnison Move clean types into their own file This PR is just about moving clean types into their own files to make the code more clear and keep all `Clean` trait implementations on their own. r? @kinnison
|
Seems like it failed in #67111 (comment) ? @bors rollup=never r- |
|
I ran it locally and no issue. The block code which failed is: I don't see how it could fail. I think the error comes from somewhere else... @bors: r=kinnison |
|
📌 Commit 12a2671 has been approved by |
Move clean types into their own file This PR is just about moving clean types into their own files to make the code more clear and keep all `Clean` trait implementations on their own. r? @kinnison
|
☀️ Test successful - checks-azure |
This PR is just about moving clean types into their own files to make the code more clear and keep all
Cleantrait implementations on their own.r? @kinnison