ucsd-progsys/liquidhaskell

Termination error messages do not follow standard GHC format

Open

#1,961 创建于 2022年4月4日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)Haskell (1,306 star) (157 fork)batch import
good first issue

描述

When checking tests/neg/AutoSize.hs, the folllowing is output:

**** LIQUID: UNSAFE ************************************************************

neg/AutoSize.hs:19:1: error:
    Termination Error
AutoSize.expSize
No decreasing parameter
   |
19 | expSize (EConst _) = 0
   | ^^^^^^^

Compare with:

**** LIQUID: UNSAFE ************************************************************

neg/Ast.hs:55:1: error:
    Liquid Type Mismatch
    .
    The inferred type
      VV : Ast.AstIndex
    .
    is not a subtype of the required type
      VV : {VV : Ast.AstIndex | Ast.isTypeIndex VV}
    .
    Constraint id 1
   |
55 | wrong = id1 astExpr
   |

and you can see the leading whitespace differences.

贡献者指南

技术栈
无
领域
developer experience
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
1
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
basic Haskell knowledgefamiliarity with GHC error format
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
90
研究方向
The issue highlights a formatting inconsistency in termination error messages. Compare the output from `tests/neg/AutoSize.hs` with the standard GHC format shown in `neg/Ast.hs`. The fix involves adjusting the whitespace and possibly the structure of termination error output in LiquidHaskell's error reporting code. Locate the function responsible for generating termination errors and modify it to align with GHC's style. Refer to the LiquidHaskell source, likely in files related to error handling, and test with the provided examples.
Termination error messages do not follow standard GHC format · ucsd-progsys/liquidhaskell#1961 | Good First Issue