Updating HasValue_OP to not propogate optional type to dot expression
When HasValue_OP was being used on a expression tyoe that was an optional, the resulting type of the dot expression also became an optional -this can be seen in the below screenshot
This made it difficult to work with since you had provide x.hashValue :? false etc everywhere
By checking the DotExpression Type system aspect i could see reference to the dot expression method neverMakeOption, which default to false but for this case HasValue presumably should be true.
Updating HasValue_OP to not propogate optional type to dot expression
When HasValue_OP was being used on a expression tyoe that was an optional, the resulting type of the dot expression also became an optional -this can be seen in the below screenshot
This made it difficult to work with since you had provide x.hashValue :? false etc everywhere
By checking the DotExpression Type system aspect i could see reference to the dot expression method neverMakeOption, which default to false but for this case HasValue presumably should be true.
I added sometests within the existing test suite