Misleading error message, privacy error reported as type error

[gnzlbg]

mod foo {
    pub struct Foo {
        private: i32,
    }
}

use foo::Foo;

fn main() {
    let mut foo = Foo { private: 0_usize };
}

(Playground)

Errors:

   Compiling playground v0.0.1 (/playground)
error[E0308]: mismatched types
  --> src/main.rs:11:34
   |
11 |     let mut foo = Foo { private: 0_usize } ;
   |                                  ^^^^^^^ expected i32, found usize

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
error: Could not compile `playground`.

To learn more, run the command again with --verbose.

The error message here is incorrect. Whether the types match or not is irrelevant, because the field is private. The error should say something like this instead (playground):

 error[E0451]: field `private` of struct `foo::Foo` is private
  --> src/main.rs:10:25
   |
10 |     let mut foo = Foo { private: 0_i32 };
   |                         ^^^^^^^^^^^^^^ field `private` is private

error: aborting due to previous error

[TheSamsa]

I would like to tackle this as a first timer, if that is okay and not too overly complicated for a first time issue ;)
A little pointer where to begin my trip would be awesome, thanks in advance!

[gnzlbg]

cc @estebank

[witling]

I would like to tackle this as a first timer, if that is okay and not too overly complicated for a first time issue ;)
A little pointer where to begin my trip would be awesome, thanks in advance!

I don't believe that this is a good first time issue. Type checking is done before executing privacy checks. (see here)
Changing the order seems to have a negative performance impact in a lot of cases as type errors seem to be way more common. At least that is what my 20 minute code skim came up to.

[TheSamsa]

I would like to tackle this as a first timer, if that is okay and not too overly complicated for a first time issue ;)
A little pointer where to begin my trip would be awesome, thanks in advance!

I don't believe that this is a good first time issue. Type checking is done before executing privacy checks. (see here)
Changing the order seems to have a negative performance impact in a lot of cases as type errors seem to be way more common. At least that is what my 20 minute code skim came up to.

Hi thank you for your insights!
I won't do it then, since my time is in short supply right now. It is better for someone else to step in.