XmlDoc is allowed before `and` in type definitions

[auduchinok]

type A = class end

/// Bbb
and
    B = class end

[auduchinok]

Another case with wrong reported xml doc range would be:

type A = class end

/// Bbb
and
/// 123
    B = class end

[cartermp]

What would you expect the result to be? I don't personally think it's an issue that you see Bbb when hovering over B

[auduchinok]

I'd not expect anything before and to belong to the declaration.
Maybe it's due to I'm used to quite strict C# rules for these comments.

[cartermp]

I guess it's a little hard to make a call when you write it like this:

I often do that, and so it feels consistent to me. But I can understand why it's weird that you can write XML docs in both places such as your sample.

[auduchinok]

OK, how about having more preceding things? 🙂

C# rules would only use the last doc comment block, i.e. /// world here.

[cartermp]

Yeah, in that case it's a quirk to be sure. But I wouldn't agree with eliminating the one with the union case either. I'll label this an improvement.