Universal impl trait shows camel case name warning

[vi]

#![feature(universal_impl_trait)]
#![feature(conservative_impl_trait)]
 
fn qqq(lol: impl Iterator<Item=u32>) -> impl Iterator<Item=u64> {
    lol.map(|x|x as u64)
}

warning: type parameter `impl Iterator<Item = u32>` should have a camel case name such as `Impl iterator<item = u32>`

[cramertj]

impl Trait in argument position now desugars to explicit type parameters at the HIR level. There are two possible fixes for this: specifically ignore impl xxx params, or move the NonCamelCaseTypes lint to run on the AST (an EarlyLintPass instead of a LateLintPass).

I'm working on this.

cc @nikomatsakis

[nikomatsakis]

Kind of amusing. Ignoring parameters tagged as synthetic seems to make sense. On Dec 22, 2017 9:10 PM, Taylor Cramer <notifications@github.com> wrote:impl Trait in argument position now desugars to explicit type parameters at the HIR level. There are two possible fixes for this: specifically ignore impl xxx params, or move the NonCamelCaseTypes lint to run on the AST (an EarlyLintPass instead of a LateLintPass). I'm working on this. cc @nikomatsakis —You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.