Skip to content

Conversation

CraftSpider
Copy link
Contributor

@CraftSpider CraftSpider commented Sep 7, 2024

Noticed while considering backtrace_in_libstd. Figured it was worth making it more clear which imports needed std, and removing some pointless casting and such.

Comment on lines +352 to +440
path.push(char::from_digit((build_id[0] >> 4) as u32, 16)?);
path.push(char::from_digit((build_id[0] & 0xf) as u32, 16)?);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, this is significantly noisier in practice... I think I'd prefer to keep fn hex.

@workingjubilee
Copy link
Member

This will conflict with #662 and was conflicted by #649

@CraftSpider
Copy link
Contributor Author

I'll fix conflict when I have a moment. Sorry for not updating yet - doing real life stuff over the weekend.

@workingjubilee
Copy link
Member

workingjubilee commented Sep 8, 2024

that's fine! I actually was speaking up because I would recommend you not update this until after #662 lands...

@workingjubilee workingjubilee merged commit a0fb196 into rust-lang:master Jan 3, 2025
75 of 88 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants