-
Notifications
You must be signed in to change notification settings - Fork 13.3k
address more FIXME whose associated issues were marked as closed #45097
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
update FIXME(rust-lang#6298) to point to open issue 15020 update FIXME(rust-lang#6268) to point to RFC 811 update FIXME(rust-lang#10520) to point to RFC 1751 remove FIXME for emscripten issue 4563 and include target in `test_estimate_scaling_factor` remove FIXME(rust-lang#18207) since node_id isn't used for `ref` pattern analysis remove FIXME(rust-lang#6308) since DST was implemented in rust-lang#12938 remove FIXME(rust-lang#2658) since it was decided to not reorganize module remove FIXME(rust-lang#20590) since it was decided to stay conservative with projection types remove FIXME(rust-lang#20297) since it was decided that solving the issue is unnecessary remove FIXME(rust-lang#27086) since closures do correspond to structs now remove FIXME(rust-lang#13846) and enable `function_sections` for windows remove mention of rust-lang#22079 in FIXME(rust-lang#22079) since this is a general FIXME remove FIXME(rust-lang#5074) since the restriction on borrow were lifted
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @pnkfelix (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
r=me once the review comments are addressed.
@@ -64,8 +64,7 @@ pub fn opts() -> TargetOptions { | |||
]); | |||
|
|||
TargetOptions { | |||
// FIXME(#13846) this should be enabled for windows | |||
function_sections: false, | |||
function_sections: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this supposed to be changed to true
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I tested this locally and it links successfully with x86_64-pc-windows-gnu
. The FIXME was about turning on the flag once it is no longer an issue.
@@ -781,8 +781,9 @@ the base path, it will still be considered freezable. | |||
|
|||
|
|||
|
|||
**FIXME #10520: Restrictions against mutating the base pointer.** When | |||
an `&mut` pointer is frozen or claimed, we currently pass along the | |||
**FIXME(https://github.com/rust-lang/rfcs/issues/1751) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given this is md, should this be a link?
**FIXME [rfcs/1751](https://github.com/rust-lang/rfcs/issues/1751)
@@ -659,7 +659,7 @@ impl<'a, 'tcx> CheckLoanCtxt<'a, 'tcx> { | |||
debug!("check_if_path_is_moved(id={:?}, use_kind={:?}, lp={:?})", | |||
id, use_kind, lp); | |||
|
|||
// FIXME (22079): if you find yourself tempted to cut and paste |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This points to a PR, not an issue. It's fine to remove as you're doing, just pointing it out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know, it's just that the FIXME is general and the number makes it seem like it is waiting on problem to be fixed.
@bors r=estebank |
📌 Commit 90f6bc0 has been approved by |
⌛ Testing commit 90f6bc0 with merge 0a2b5c7bdddcdcfda10e07f4748ebab37b60aa6c... |
💔 Test failed - status-appveyor |
|
guess not, didn't test thoroughly enough. Reverted change |
@bors r+ rollup |
📌 Commit 094c2ae has been approved by |
address more FIXME whose associated issues were marked as closed part of rust-lang#44366
part of #44366