(Split off from discussion on #56188.)
There are a few places where the path std::prelude::v1 appears in diagnostic messages.
zmd@ReflectiveCoherence:~/Code/rust/src/test/ui$ ag std::prelude
[...]
27 matches
9 files contained matches
I argue that this is bad because the point of the prelude is to relieve the ordinary programmer from having to think about where necessities like Some and Vec live; the module std::prelude::v1 is an implementation detail that should be mentioned in places like the Book, but which I don't want to see cluttering up error messages.
We are manually stripping off the std::prelude::v1:: in a couple places (one, another proposed in open PR #56188), but we should:
(Split off from discussion on #56188.)
There are a few places where the path
std::prelude::v1appears in diagnostic messages.I argue that this is bad because the point of the prelude is to relieve the ordinary programmer from having to think about where necessities like
SomeandVeclive; the modulestd::prelude::v1is an implementation detail that should be mentioned in places like the Book, but which I don't want to see cluttering up error messages.We are manually stripping off the
std::prelude::v1::in a couple places (one, another proposed in open PR #56188), but we should:std::prelude::v1::for all diagnostic messages