You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Determine whether we need a node ID when resolving methods #4951
Triage: FIXME is still there. I guess having a NodeId would make other tooling easier, e.g. #8961 would likely be easier to fix if every method had an associated NodeId (since it would then not require (as much) special casing).
Activity
msullivan commentedon Jul 1, 2013
FIXME still there. We probably don't need a node_id, if it actually works...
emberian commentedon Aug 19, 2013
/cc @pcwalton
huonw commentedon Nov 10, 2013
Triage: FIXME is still there. I guess having a NodeId would make other tooling easier, e.g. #8961 would likely be easier to fix if every method had an associated NodeId (since it would then not require (as much) special casing).
steveklabnik commentedon Aug 12, 2014
For future spelunkers, this is talking about
rust/src/librustc/middle/resolve.rs
Line 3724 in e2273d9
Rollup merge of rust-lang#26889 - sanxiyn:fixme, r=alexcrichton
Merge pull request rust-lang#4951 from KMiri-rs/stack-borrow-bitfields
Merge rust-lang#4951
Move toolchain, Kani and Flux to nightly-2026-09-25
Merge subtree update for toolchain nightly-2026-09-25 (model-checking…