Hacker News Reader

Comment by verandaguy | Hacker News Reader

Having worked with rust for nearly two years now (granted, on one team with agreed-upon standards):

- glob imports are rare in my experience, less for the LSP’s sake and more for code self-documentation

- the `mod foo` line exists because omitting it cannot fall back to a reasonable default visibility level (`pub`/`pub(crate)`/<none> (private))

Of course it could just default to private, and if you wanted something you'd have to specify that.

At this point...

- I don't think that private-default is a universally (or more importantly, widely) reasonable default

- It adds another case where Rust is unopinionated and gives the user another way to do a basic function.

I like Rust for its unopionation, generally, but I think that the returns for this kind of thing diminish as you get to really boilerplate stuff.

I'll argue the default already is private.

  mod foo
  pub mod foo
  pub(crate) mod foo

clearly when you leave the visibility modifier out, the default is private.