racket / racket/htdp

new check-expect output with large values is hard to read

Open
#122 2 comments 0 reactions 1 assignee View on GitHub

@mikesperber is already working on this.

Since Nov 25, 2020.

test engine
Dominant language
Racket
Stars
112
Forks
73
Avg merge
9h 41m
Merged PRs (30d)
1

Description

Consider this program

#lang htdp/asl

(check-expect (build-list 20 (lambda (x) x))
              (build-list 21 (lambda (x) x)))

It prints:

[samth@huor:~/sw/plt (master) plt] raco test /tmp/d.rkt 
raco test: (submod "/tmp/d.rkt" test)
Ran 1 test.                                                                                                                                                                        
0 tests passed.                                                                                                                                                                    
Check failures:                                                                                                                                                                    
                     ┌──────────────────────────────────────────────────────────┐              ┌─────────────────────────────────────────────────────────────┐                     
        Actual value │ (list 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19) │ differs from │ (list 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20) │, the expected value.
                     └──────────────────────────────────────────────────────────┘              └─────────────────────────────────────────────────────────────┘                     
        in d.rkt, line 3, column 0         

which is not great in a window that wraps, such as almost every terminal.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.