Incorrect analysis of expression-bodied read-only properties.

[KFAFSP]

When defining a read-only expression-bodied property, Exceptional fails to recognize the throw statement in the expression and indicates that I documented an exception that is not thrown.

Example:

/// <exception cref="InvalidOperationException">Optional is absent.</exception>
public T Value => IsPresent ? Unpack : throw new InvalidOperationException(C_Absent);

This consistently happens. It does work for expression-bodied properties that do not omit the get and the block that goes with it (but I consider that inconsistent style for these properties).