Closed CobaltCause closed 1 year ago
Yes, I actually expected to see the proc-macros and proc-macros-impl crates be consolidated here.
Done, although I just did it as "stupidly" as possible which caused some tests to go away. But I think what got deleted is duplicated here anyway:
Let me know if I need to add it back.
Can you use git mv for a cleaner diff? I suspect that the two files that were detected as deleted would be more accurately described as moved.
Please correct me if I'm wrong.
(If not familiar, you can do this in an interactive rebase (git rebase -i master). When it gets to that commit, git reset
the deleted files to un-record the deletions, copy the files from impl back to proc-macros in your working tree, git rm
the copies in proc-macros and git mv
the copies in impl to proc-macros.)
On Thu, Jun 15, 2023, 2:26 PM Charles Hall @.***> wrote:
Done, although I just did it as "stupidly" as possible which caused some tests to go away. But I think what got deleted is duplicated here anyway:
— Reply to this email directly, view it on GitHub https://github.com/lloydmeta/frunk/pull/214#issuecomment-1593538824, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKYRUF2I7N2G7EUNRZOIO3XLNHU7ANCNFSM6AAAAAAZG7TXIQ . You are receiving this because you were mentioned.Message ID: @.***>
Hmm, git mv
doesn't seem to make a difference in how git shows the diff. I think there'd have to be separate delete, move, and (maybe) edit commits for git to realize they were mostly just renamed, but not sure.
Okay, the way it is is fine then. I'll take a closer look in a sec.
think there'd have to be separate delete, move, and (maybe) edit commits for git to realize they were mostly just renamed, but not sure.
You definitely don't need separate move and edit commits as long as a decent portion of the file is unchanged (if it changes little enough you don't even need git mv
for it to detect the move), but you might be right about the delete.
Okay, here's a more accurate diff of the files.
All looks good to me, only question is whether proc-macros/Cargo.toml
should still have [dev-dependencies.frunk]
since I think it no longer makes use of it. Or a small test using it could be shoehorned in. I don't have a strong feeling either way.
I think it no longer makes use of it
I just tested and this is true, I've just removed it in a force-push.
It's a bit late here, so I'll cut a release some time this weekend. Thanks!
Fixes #213.
I also noticed
but unfortunately the effects of this seem to show up in the public API.