Skip to content

Pretty printing of Absyn in error message does not respect fixity #141

Closed

Description

@JohnReppy

Version

110.82

Operating System

  • All
  • Linux
  • macOS
  • Windows
  • Other Unix

OS Version

No response

Processor

Any

Component

Core system

Severity

Cosmetic

Description of the problem

The error message prints '::' as a prefix operator, instead of as an infix operator. This behavior is a regression, since previous versions got it right (see tests/bugs/outputs/bug0027.out for example).

Transcript

Standard ML of New Jersey v110.82 [built: Sat Oct 14 13:08:58 2017]
- fun f [] = 0
=   | f (x::xs) y = 1;
stdIn:1.6-2.20 Error: clauses don't all have same number of patterns
stdIn:1.6-2.20 Error: parameter or result constraints of clauses don't agree [tycon mismatch]
  this clause:      'Z list * 'Y -> 'X
  previous clauses:      'W list -> 'X
  in declaration:
    f = (fn nil => 0
          | (:: <pat>,y) => 1)

Expected Behavior

No response

Steps to Reproduce

fun f [] = 0
| f (x::xs) y = 1;

Additional Information

No response

Email address

No response

Comments from smlnj-gforge

Original smlnj-gforge bug number 204

Submitted on 2018-37-19 at 14:3700

Keywords: Pretty printing

Activity

  1. added
    bugSomething isn't working
    compilerproblem with compiler
    gforgebug (or feature request) ported from smlnj-gforge repository
    on Jul 16, 2022
  2. dmacqueen commented on Jul 22, 2022

    @dmacqueen
    Contributor

    Fixed in 2022.1 (as well as smlnj/legacy). Used new function AbsynUtil.headStripPat in PPAbsyn..ppDconPat to strip MARKpat from the argument pattern in the APPpat case of ppDconPat'. Fix modifies ElabData/syntax/ppabsyn.sml and absynutil.sml. Also moved some PPAbsyn debug and print flags to ElabDataControl (ElabData/main/edcontrol.*.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingcompilerproblem with compilerfixed-in-2022.1Issues that have been closed for the 2022.1 releasegforgebug (or feature request) ported from smlnj-gforge repository

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions