It looks like the detection is implemented and working. Only "additional recompute" is missing as simply by closing/opening the sketch the redundant constraint will be reported!What it looks like this is more of redundant constraint detection issue indeed. For example in sketcher fully constrained vertical line can be made. Adding new line to the sketch where we add coincident constraints between the end points of both lines should produce fully constrained sketch as it does. Adding additional vertical constraint to this second line should probably be detected as redundant constraints? Or is there a reason it is not and it was done like this intentionally?
Here i am guessing not only "additional recompute" is missing but additional logic to always mark horizontal/vertical constraint as redundant in this specific scenario:Here is where we can observe redundant horizontal/vertical constraint is not detected and as result we get mentioned behavior. Probably it shouldn't be possible for the user to add horizontal/vertical constraint for the line where both end point are coincident or fixed onto external geometry line? As external geometry line (parent) will control the angle or vertical/horizontal position in the first place and a child could be trying to override this unsuccessfully with added horizontal/vertical constraint therefore resulting in breakage.
If both end points of a "child" line are coincident or fixed onto external geometry "parent" line any additional horizontal/vertical "child" line constraint should be detected and reported as redundant.
Added correction:
I believe we are talking about over-constrained sketch in this specific case and not about sketch containing redundant constraints!