1
0
mirror of https://github.com/vlang/v.git synced 2023-08-10 21:13:21 +03:00
v/vlib/compiler/tests/repl
2020-01-07 12:26:49 +01:00
..
runner os, filepath: reorganize functions 2019-12-23 13:09:22 +03:00
.gitattributes
.gitignore
arr_decl.repl
bad_in_type.repl parser: check types in a in b expressions 2019-12-04 22:17:24 +03:00
chained_fields.correct.repl
chained_fields.repl fix 2 repl tests 2019-12-18 05:02:23 +03:00
conditional_blocks.repl
default_printing.repl
empty_struct.repl
error_nosave.repl update repls tests 2019-11-13 20:40:01 +03:00
error.repl parser: undefined error 2019-10-20 20:47:27 +03:00
function.repl
immutable_len_fields.repl fix 2 repl tests 2019-12-18 05:02:23 +03:00
interpolation.repl
multiple_decl.repl
multiple_println.repl
naked_strings.repl
newlines.repl
nomain.repl
nothing.repl
option.repl foo()? test 2019-11-18 12:11:25 +03:00
postfix_operators.repl post increment/decrement repl fix 2020-01-07 12:26:49 +01:00
println.repl
README.md
repl_test.v tests: improved test output formatting 2019-12-30 05:23:54 +01:00
run.v tests: improved test output formatting 2019-12-30 05:23:54 +01:00
var_decl.repl

V REPL Tests Script

How to write a new test

  • Create a new file named *.repl
  • Write the input to be given to REPL
  • Add ===output===
  • Write the output expected

Notes

Keep in mind, that the way V repl works for now, every non empty line would cause a new recompilation of the entire repl content that was collected so far.

Longer REPL files would cause measurably longer recompilation/testing times.

Also, longer repl files would be slower to debug when they fail, It is better to have several smaller files vs one huge REPL file.

Example :

a := 1
println(a)
===output===
1