Update RFC and tracking issue numbers

text/0000-import-trait-associated-functions.md → text/3591-import-trait-associated-functions.md

@@ -1,7 +1,7 @@
 - Feature Name: `import-trait-associated-functions`
 - Start Date: 2024-03-19
-- RFC PR: [rust-lang/rfcs#0000](https://github.com/rust-lang/rfcs/pull/0000)
-- Rust Issue: [rust-lang/rust#0000](https://github.com/rust-lang/rust/issues/0000)
+- RFC PR: [rust-lang/rfcs#3591](https://github.com/rust-lang/rfcs/pull/3591)
+- Rust Issue: [rust-lang/rust#134691](https://github.com/rust-lang/rust/issues/134691)
 
 # Summary
 [summary]: #summary
@@ -268,4 +268,4 @@ As mentioned in [motivation], there was a rejected [RFC](https://github.com/rust
 
 This RFC does not propose the ability to import `Type::method` where `method` is contained in an `impl` block. Such a feature would be a natural extension of this work, and would enable numeric features like that discussed in [motivation] without the need for the [num_traits](https://docs.rs/num-traits/latest/num_traits/) crate. This feature is not proposed in this RFC since initial investigations revealed that it would be [difficult](https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang/topic/Writing.20an.20RFC.20for.20.60use.20Default.3A.3Adefault.60/near/427804375) to implement in today's rustc.
 
-If we add a compatibility mechanism to implement a supertrait method when implementing its subtrait, without having to separately implement the supertrait (such that a new supertrait can be extracted from a trait without breaking compatibility), we would also need to lift the limitation on using a supertrait method via a subtrait.
+If we add a compatibility mechanism to implement a supertrait method when implementing its subtrait, without having to separately implement the supertrait (such that a new supertrait can be extracted from a trait without breaking compatibility), we would also need to lift the limitation on using a supertrait method via a subtrait.