On 3/27/20 12:20 AM, Patrick Palka wrote:
On Mon, 9 Mar 2020, Patrick Palka wrote:
The first patch tries to avoid changing our current default diagnostics. But
for the sake of consistency we arguably should also respect
current_constraint_diagnosis_depth in diagnose_compound_requirement()
On Mon, 9 Mar 2020, Patrick Palka wrote:
> The first patch tries to avoid changing our current default diagnostics. But
> for the sake of consistency we arguably should also respect
> current_constraint_diagnosis_depth in diagnose_compound_requirement() like we
> do
> in the other
The first patch tries to avoid changing our current default diagnostics. But
for the sake of consistency we arguably should also respect
current_constraint_diagnosis_depth in diagnose_compound_requirement() like we do
in the other error-replaying diagnostic routine. But doing so would be a
