Missing check for naming conflicts between field names and literals

[treiher]

package Test is

   type C is (A => 206, B => 183) with Size => 54, Always_Valid => True;
   type D is range 48 .. 54 with Size => 6;
   type E is
      message
         A : C;
         B : D;
      end message;

end Test;

model: error: contradicting condition in "Test.E"
tmp/test.rflx:3:4: model: info: unsatisfied "B = 183"
tmp/test.rflx:4:4: model: info: unsatisfied "B <= 54"
model: error: contradicting condition in "Test.E"
tmp/test.rflx:7:10: model: info: on path: "A"
tmp/test.rflx:3:4: model: info: unsatisfied "B = 183"
tmp/test.rflx:4:4: model: info: unsatisfied "B <= 54"
model: error: contradicting condition in "Test.E"
tmp/test.rflx:7:10: model: info: on path: "A"
tmp/test.rflx:8:10: model: info: on path: "B"
tmp/test.rflx:3:4: model: info: unsatisfied "B = 183"
tmp/test.rflx:4:4: model: info: unsatisfied "B <= 54"

[senier]

I don't think this is just an unclear error message. Rather we seem not to detect the conflict between field name and literal at all. The error just happens to be detected by coincidence - if e.g. type D had a range of 183..183 bad things will happen further down the road.

[treiher]

You are right. I have changed the issue title.