Idris2/tests/chez/chez027/expected

1/1: Building StringParser (StringParser.idr)
Main> hiya
2
Parse failed at position 0-0: could not satisfy predicate
Parse failed at position 0-0: Not good
['7', '6', '6', '7', '7', '5']
['6', '3', '5', '5', '3']
"887"
"XML Comment"
"<- Complicated -- XML -- Comment ->"
Parse failed at position 0-24: end of string reached - "-->" not found
"123"
""
True
False
['a', '1', 'b', '2']
['a', 12, 'b', 3, 'c']
['a', 'b', 'c', 'd']
()
Parse failed at position 0-0: Purposefully changed OK to Fail
Main> Bye for now!
Flush standard out after writing prompt to it On Unix-like operating systems stdio.h is usually line-buffered. As putStr uses fputs(3) from stdio.h internally, output will be written to standard out after a newline character is written to the buffer. Since the prompt does not contain a newline, it will only be written to standard output after the user presses return. I encountered this issue on Alpine Linux which uses musl libc (instead of glibc). However, I believe this issue is likely also reproducible with glibc. This commit fixes this issue by flushing standard output after writing the prompt to it. Surprisingly, `src/Idris/IDEMode/REPL.idr` already does this correctly, `src/Idris/REPL.idr` does not though. 2021-02-28 05:00:20 +03:00			`1/1: Building StringParser (StringParser.idr)`
			`Main> hiya`
Add test and documentation 2020-07-05 17:39:34 +03:00			`2`
Show the line and column in diagnostic message This also updates the error message of some common combinators 2021-11-02 03:32:24 +03:00			`Parse failed at position 0-0: could not satisfy predicate`
			`Parse failed at position 0-0: Not good`
Add test and documentation 2020-07-05 17:39:34 +03:00			`['7', '6', '6', '7', '7', '5']`
			`['6', '3', '5', '5', '3']`
			`"887"`
Add takeUntil Data.String.Parser parser 2021-10-22 18:33:14 +03:00			`"XML Comment"`
			`"<- Complicated -- XML -- Comment ->"`
Show the line and column in diagnostic message This also updates the error message of some common combinators 2021-11-02 03:32:24 +03:00			`Parse failed at position 0-24: end of string reached - "-->" not found`
Add test and documentation 2020-07-05 17:39:34 +03:00			`"123"`
			`""`
			`True`
			`False`
Add extra parsers This also changes the return type of `char` and `string`. They previously returned `()`, they now return `Char` and `String` repectively. Signed-off-by: Alex Humphreys <alex.humphreys@here.com> 2020-11-23 21:12:39 +03:00			`['a', '1', 'b', '2']`
[ contrib ] Alternating lists of known parity (#2043) 2021-10-30 02:12:44 +03:00			`['a', 12, 'b', 3, 'c']`
Add extra parsers This also changes the return type of `char` and `string`. They previously returned `()`, they now return `Char` and `String` repectively. Signed-off-by: Alex Humphreys <alex.humphreys@here.com> 2020-11-23 21:12:39 +03:00			`['a', 'b', 'c', 'd']`
			`()`
Show the line and column in diagnostic message This also updates the error message of some common combinators 2021-11-02 03:32:24 +03:00			`Parse failed at position 0-0: Purposefully changed OK to Fail`
Flush standard out after writing prompt to it On Unix-like operating systems stdio.h is usually line-buffered. As putStr uses fputs(3) from stdio.h internally, output will be written to standard out after a newline character is written to the buffer. Since the prompt does not contain a newline, it will only be written to standard output after the user presses return. I encountered this issue on Alpine Linux which uses musl libc (instead of glibc). However, I believe this issue is likely also reproducible with glibc. This commit fixes this issue by flushing standard output after writing the prompt to it. Surprisingly, `src/Idris/IDEMode/REPL.idr` already does this correctly, `src/Idris/REPL.idr` does not though. 2021-02-28 05:00:20 +03:00			`Main> Bye for now!`