d679146a80 | ||
---|---|---|
.. | ||
chained_fields | ||
conditional_blocks | ||
immutable_len_fields | ||
runner | ||
.gitattributes | ||
.gitignore | ||
README.md | ||
array_filter.repl | ||
array_init.repl | ||
bad_in_type.repl.skip | ||
default_printing.repl | ||
empty_struct.repl.skip | ||
entire_commented_module.repl | ||
error.repl | ||
error_nosave.repl.skip | ||
fn_calls.repl | ||
function.repl.skip | ||
import.repl | ||
import_alias.repl | ||
naked_strings.repl | ||
newlines.repl | ||
nomain.repl | ||
nothing.repl | ||
open_close_string_check.repl | ||
option.repl.skip | ||
optional_call.repl | ||
postfix_operators.repl | ||
println.repl | ||
repl_test.v | ||
var_decl.repl | ||
void_vlib_fncall.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