-
Notifications
You must be signed in to change notification settings - Fork 206
Rename crate::exid::ExId to crate::obj_id::ObjId #755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Now, the interesting question is whether this has any compatibility effects. It seems like it should definitely not, because the exported name and type have not changed, but I am cautious. @teohhanhui did you encounter anywhere when you wrote code against this library that had to use |
b69fdfe
to
a73b3dc
Compare
If we used type alias it'd have compatibility concerns: https://predr.ag/blog/re-exporting-enum-with-type-alias-breaking-change-not-major/ But we didn't. There are no compatibility concerns that I'm aware of.
No. |
This change doesn't fix everything. Wherever |
a73b3dc
to
15363d9
Compare
15363d9
to
4039dcb
Compare
Can you elaborate? |
e.g. automerge/rust/automerge/src/autocommit.rs Line 574 in 9400e19
results in but it links correctly to So what this PR achieves is pretty minimal. I've limited myself to only getting rid of any mention of |
Looks like that will be fixed soon: rust-lang/rust#113374 |
Hmm, do we need to make this change then? |
In the linked PR, I don't see any tests for |
Looks like that's rust-lang/rust#41072 |
I'm inclined to think that this is a rustdoc bug and we should just wait for it to be fixed as even with these changes we end up with |
No description provided.