v/compiler/tests/repl
Delyan Angelov 854de4e7e0 repl: add more stats and tests; compiler: tcc fixes 2019-09-16 00:41:12 +03:00
..
runner repl: add some timing statistics when running REPL test files 2019-09-15 18:08:16 +03:00
.gitattributes
.gitignore repl: add some timing statistics when running REPL test files 2019-09-15 18:08:16 +03:00
README.md repl: add more stats and tests; compiler: tcc fixes 2019-09-16 00:41:12 +03:00
arr_decl.repl
chained_fields.correct.repl repl: add more stats and tests; compiler: tcc fixes 2019-09-16 00:41:12 +03:00
chained_fields.repl
conditional_blocks.repl
default_printing.repl
empty_struct.repl repl: add more stats and tests; compiler: tcc fixes 2019-09-16 00:41:12 +03:00
error.repl
error_nosave.repl
function.repl
immutable_len_fields.repl repl: add more stats and tests; compiler: tcc fixes 2019-09-16 00:41:12 +03:00
interpolation.repl
multiple_decl.repl
multiple_println.repl
naked_strings.repl
newlines.repl
nothing.repl
println.repl
repl_test.v repl: add more stats and tests; compiler: tcc fixes 2019-09-16 00:41:12 +03:00
run.v repl: add some timing statistics when running REPL test files 2019-09-15 18:08:16 +03:00
var_decl.repl

README.md

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