URI conflict validation is too constraining

Minimised repro

namespace foo

service Foo {
  operations: [Hello1, Hello2]
}

structure Hello1Input {
  @httpLabel
  @required
  name: String,
}

@http(method: "GET", uri: "/hello")
@readonly
operation Hello2 {
}

@http(method: "GET", uri: "/{name}/greet")
operation Hello1 {
  input: Hello1Input,
}

Gives the following errors :

Expected behaviour :

These two URI paths should not be presenting a conflict, as there is always a possibility to distinguish between one and the other without additional informations.

I believe the cause of the problem is this condition which rakes too widely.

[mtdowling]

Yes, it is too constraining in several ways. We have a few proposals to make URI conflict resolution more flexible. I’m hoping we can finish those up and publish an RFC soon.

[david-perez]

Is that RFC ready?