-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Update Path
constructor to new conventions
#5389
Comments
More or less blocked on #4202 |
@brson I did some investigatory digging into this issue with my fix for #4202 in place & unfortunately I suspect that reexports of traits are still broken enough in certain cases that Path::new won't work. That said, I do plan to dig deeper into the underlying issues with trait reexports once my girlfriend forgives me for the past ~week or so of neglect. :P |
My earlier fix for #4202 would not work correctly if the trait being exported was a top-level item relative to the module from which it was being exported. An example that would not work correctly with the original patch: // foo.rs pub use Foo = self::Bar; pub trait Bar { pub fn bar() -> Self; } impl Bar for int { pub fn bar() -> int { 42 } } // bar.rs fn main() { foo::Foo::bar() } This is now supported. I believe this change will allow the GenericPath trait to be exported from core::path as Path in such a manner, which should allow #5389 to move forward.
@brson to be crystal clear: we're essentially removing WindowsPath & PosixPath methods, aliasing GenericPath as Path with a "pub use ..." & renaming GenericPath::from_str to GenericPath::new here, right? |
revisiting for triage. seems correctly nominated and still an issue. |
Fix ICE in consts::binop changelog: Fix ICE in `consts::binop` Fixes rust-lang#5389
* config_proc_macro: fix failing doctests * ci: include config_proc_macro crate in ci * [review] working native windows ci * [fix] add --locked file for ci * [fix] quoting of cmd variables
Should have a static
new
method.Subset of #3853
The text was updated successfully, but these errors were encountered: