Owen Avery

I found a few related attribute issues with https://godbolt.org/z/9rPG9Wr1j - [ ] #2087 - [ ] #2088 - [ ] #2089 - [ ] #2090

I've written the following patch for Gentoo ``` --- a/src/tools/cargo/src/cargo/ops/lockfile.rs +++ b/src/tools/cargo/src/cargo/ops/lockfile.rs @@ -36,6 +36,11 @@ pub fn resolve_to_string(ws: &Workspace, resolve: &mut Resolve) -> CargoResult { + // prevent lock...

Up-to-date patch, if anyone wants it. Could probably be reworked for nix ``` --- a/src/tools/cargo/src/cargo/ops/lockfile.rs +++ b/src/tools/cargo/src/cargo/ops/lockfile.rs @@ -38,6 +38,11 @@ /// Returns `true` if the lockfile changed #[tracing::instrument(skip_all)] pub...

You'd probably want to make ```Function``` inherit from ```ExternalItem```

I'm pretty sure you can fix ambiguous functions by overriding them in ```Function```, which wouldn't be ideal, but might be the best option.

It doesn't look like the types of external function parameters are being resolved. Either that, or external items in the ```extern "C" {}``` block aren't being resolved. What happens if...

You'd also need to fix the build errors and format the commit messages

Looks good. You might want to split off some of these commits into separate pull requests, so that they can get reviewed/merged faster -- that's what I tend to do

It looks like https://github.com/CohenArthur/gccrs/commit/f4a2ae2338962208b8039f154f5912402e94c378 broke the formatting

https://godbolt.org/z/sThP53WbG ```rust pub fn main() { let _a = 1..=0; match 0 { 1..=0 => {}, _ => {} } let (1..=0, _b) = (1, 0); } ``` It looks...