CatalaLang/catala
1
1
Fork 0
mirror of https://github.com/CatalaLang/catala.git synced 2024-11-09 01:35:56 +03:00
Code Issues Projects Releases Wiki Activity
429911024c
catala/tests/test_variable_state/bad/state_cycle.catala_en

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

83 lines
2.0 KiB
Plaintext
Raw Normal View History

Cycle test
2022-03-06 19:34:51 +03:00
## Test
```catala
declaration scope A:
output foo content integer
state bar
state baz
output foofoo content integer
state bar
state baz
scope A:
definition foo state bar equals foofoo
definition foo state baz equals foo + 1
definition foofoo state bar equals foo
definition foofoo state baz equals foofoo + 1
```
Register all existing tests through the new engine I removed the '.out' extension for now to preserve the test output file names and avoid a million file renames. This makes the patch easier to read, and we can do the rename easily in another patch afterwards, without mixing with semantic changes. (beautiful script àlarrache: ```bash for f in */*/output/*; do target_base=${f##*/} target_base=${target_base%%.*} echo $f | awk -F. '{ f=$1"."$2; if ($4 == "") { mode=$3; id=$3 } else { scope="-s "$3; mode=$4; id=$3"."$4} printf "\n```catala-test {id=\"%s\"}\ncatala %s %s\n```\n",id,mode,scope; }' >> $(dirname $f)/../${target_base}.*; done ```
2022-07-08 17:23:09 +03:00
Turn all existing tests to inline tests Done using ```bash process() { FILE=$1; awk 'match($0, /^```catala-test *{ *id *= *"(.*)" *}/, a) {print "```catala-test-inline"; f="'"$(dirname $FILE)/output/$(basename $FILE)"'." a[1]; getline; print "$ " $0; while ((getline<f) > 0) print; next} {print}' $FILE >$FILE.new; mv $FILE.new $FILE; } for f in tests/test_*/*/*.catala_* examples/**/*.catala_*; do process $f; git add $f; done for d in $(find -name output -type d); do git rm -r $d; done ```
2022-09-23 15:04:13 +03:00
```catala-test-inline
$ catala Typecheck
[ERROR] Cyclic dependency detected between variables of scope A!
Cycle variable foofoo.bar, declared:
Add parseable line-column info to error messages a quick fix for now, ideally we want an option for editor-friendly output. But for now this is a very cheap way to at least have clickable error messages which are a big time-saver.
2022-10-27 13:10:23 +03:00
--> tests/test_variable_state/bad/state_cycle.catala_en:9.10-13
Tests: cleanup remaining whitespace
2022-09-26 15:27:47 +03:00
|
Turn all existing tests to inline tests Done using ```bash process() { FILE=$1; awk 'match($0, /^```catala-test *{ *id *= *"(.*)" *}/, a) {print "```catala-test-inline"; f="'"$(dirname $FILE)/output/$(basename $FILE)"'." a[1]; getline; print "$ " $0; while ((getline<f) > 0) print; next} {print}' $FILE >$FILE.new; mv $FILE.new $FILE; } for f in tests/test_*/*/*.catala_* examples/**/*.catala_*; do process $f; git add $f; done for d in $(find -name output -type d); do git rm -r $d; done ```
2022-09-23 15:04:13 +03:00
9 | state bar
| ^^^
+ Test
Used here in the definition of another cycle variable foofoo.baz:
Add parseable line-column info to error messages a quick fix for now, ideally we want an option for editor-friendly output. But for now this is a very cheap way to at least have clickable error messages which are a big time-saver.
2022-10-27 13:10:23 +03:00
--> tests/test_variable_state/bad/state_cycle.catala_en:19.37-43
Tests: cleanup remaining whitespace
2022-09-26 15:27:47 +03:00
|
Turn all existing tests to inline tests Done using ```bash process() { FILE=$1; awk 'match($0, /^```catala-test *{ *id *= *"(.*)" *}/, a) {print "```catala-test-inline"; f="'"$(dirname $FILE)/output/$(basename $FILE)"'." a[1]; getline; print "$ " $0; while ((getline<f) > 0) print; next} {print}' $FILE >$FILE.new; mv $FILE.new $FILE; } for f in tests/test_*/*/*.catala_* examples/**/*.catala_*; do process $f; git add $f; done for d in $(find -name output -type d); do git rm -r $d; done ```
2022-09-23 15:04:13 +03:00
19 | definition foofoo state baz equals foofoo + 1
| ^^^^^^
+ Test
Cycle variable foofoo.baz, declared:
Add parseable line-column info to error messages a quick fix for now, ideally we want an option for editor-friendly output. But for now this is a very cheap way to at least have clickable error messages which are a big time-saver.
2022-10-27 13:10:23 +03:00
--> tests/test_variable_state/bad/state_cycle.catala_en:10.10-13
Tests: cleanup remaining whitespace
2022-09-26 15:27:47 +03:00
|
Turn all existing tests to inline tests Done using ```bash process() { FILE=$1; awk 'match($0, /^```catala-test *{ *id *= *"(.*)" *}/, a) {print "```catala-test-inline"; f="'"$(dirname $FILE)/output/$(basename $FILE)"'." a[1]; getline; print "$ " $0; while ((getline<f) > 0) print; next} {print}' $FILE >$FILE.new; mv $FILE.new $FILE; } for f in tests/test_*/*/*.catala_* examples/**/*.catala_*; do process $f; git add $f; done for d in $(find -name output -type d); do git rm -r $d; done ```
2022-09-23 15:04:13 +03:00
10 | state baz
| ^^^
+ Test
Used here in the definition of another cycle variable foo.bar:
Add parseable line-column info to error messages a quick fix for now, ideally we want an option for editor-friendly output. But for now this is a very cheap way to at least have clickable error messages which are a big time-saver.
2022-10-27 13:10:23 +03:00
--> tests/test_variable_state/bad/state_cycle.catala_en:13.34-40
Tests: cleanup remaining whitespace
2022-09-26 15:27:47 +03:00
|
Turn all existing tests to inline tests Done using ```bash process() { FILE=$1; awk 'match($0, /^```catala-test *{ *id *= *"(.*)" *}/, a) {print "```catala-test-inline"; f="'"$(dirname $FILE)/output/$(basename $FILE)"'." a[1]; getline; print "$ " $0; while ((getline<f) > 0) print; next} {print}' $FILE >$FILE.new; mv $FILE.new $FILE; } for f in tests/test_*/*/*.catala_* examples/**/*.catala_*; do process $f; git add $f; done for d in $(find -name output -type d); do git rm -r $d; done ```
2022-09-23 15:04:13 +03:00
13 | definition foo state bar equals foofoo
| ^^^^^^
+ Test
Cycle variable foo.bar, declared:
Add parseable line-column info to error messages a quick fix for now, ideally we want an option for editor-friendly output. But for now this is a very cheap way to at least have clickable error messages which are a big time-saver.
2022-10-27 13:10:23 +03:00
--> tests/test_variable_state/bad/state_cycle.catala_en:6.10-13
Tests: cleanup remaining whitespace
2022-09-26 15:27:47 +03:00
|
Turn all existing tests to inline tests Done using ```bash process() { FILE=$1; awk 'match($0, /^```catala-test *{ *id *= *"(.*)" *}/, a) {print "```catala-test-inline"; f="'"$(dirname $FILE)/output/$(basename $FILE)"'." a[1]; getline; print "$ " $0; while ((getline<f) > 0) print; next} {print}' $FILE >$FILE.new; mv $FILE.new $FILE; } for f in tests/test_*/*/*.catala_* examples/**/*.catala_*; do process $f; git add $f; done for d in $(find -name output -type d); do git rm -r $d; done ```
2022-09-23 15:04:13 +03:00
6 | state bar
| ^^^
+ Test
Used here in the definition of another cycle variable foo.baz:
Add parseable line-column info to error messages a quick fix for now, ideally we want an option for editor-friendly output. But for now this is a very cheap way to at least have clickable error messages which are a big time-saver.
2022-10-27 13:10:23 +03:00
--> tests/test_variable_state/bad/state_cycle.catala_en:15.34-37
Tests: cleanup remaining whitespace
2022-09-26 15:27:47 +03:00
|
Turn all existing tests to inline tests Done using ```bash process() { FILE=$1; awk 'match($0, /^```catala-test *{ *id *= *"(.*)" *}/, a) {print "```catala-test-inline"; f="'"$(dirname $FILE)/output/$(basename $FILE)"'." a[1]; getline; print "$ " $0; while ((getline<f) > 0) print; next} {print}' $FILE >$FILE.new; mv $FILE.new $FILE; } for f in tests/test_*/*/*.catala_* examples/**/*.catala_*; do process $f; git add $f; done for d in $(find -name output -type d); do git rm -r $d; done ```
2022-09-23 15:04:13 +03:00
15 | definition foo state baz equals foo + 1
| ^^^
+ Test
Cycle variable foo.baz, declared:
Add parseable line-column info to error messages a quick fix for now, ideally we want an option for editor-friendly output. But for now this is a very cheap way to at least have clickable error messages which are a big time-saver.
2022-10-27 13:10:23 +03:00
--> tests/test_variable_state/bad/state_cycle.catala_en:7.10-13
Tests: cleanup remaining whitespace
2022-09-26 15:27:47 +03:00
|
Turn all existing tests to inline tests Done using ```bash process() { FILE=$1; awk 'match($0, /^```catala-test *{ *id *= *"(.*)" *}/, a) {print "```catala-test-inline"; f="'"$(dirname $FILE)/output/$(basename $FILE)"'." a[1]; getline; print "$ " $0; while ((getline<f) > 0) print; next} {print}' $FILE >$FILE.new; mv $FILE.new $FILE; } for f in tests/test_*/*/*.catala_* examples/**/*.catala_*; do process $f; git add $f; done for d in $(find -name output -type d); do git rm -r $d; done ```
2022-09-23 15:04:13 +03:00
7 | state baz
| ^^^
+ Test
Used here in the definition of another cycle variable foofoo.bar:
Add parseable line-column info to error messages a quick fix for now, ideally we want an option for editor-friendly output. But for now this is a very cheap way to at least have clickable error messages which are a big time-saver.
2022-10-27 13:10:23 +03:00
--> tests/test_variable_state/bad/state_cycle.catala_en:17.37-40
Tests: cleanup remaining whitespace
2022-09-26 15:27:47 +03:00
|
Turn all existing tests to inline tests Done using ```bash process() { FILE=$1; awk 'match($0, /^```catala-test *{ *id *= *"(.*)" *}/, a) {print "```catala-test-inline"; f="'"$(dirname $FILE)/output/$(basename $FILE)"'." a[1]; getline; print "$ " $0; while ((getline<f) > 0) print; next} {print}' $FILE >$FILE.new; mv $FILE.new $FILE; } for f in tests/test_*/*/*.catala_* examples/**/*.catala_*; do process $f; git add $f; done for d in $(find -name output -type d); do git rm -r $d; done ```
2022-09-23 15:04:13 +03:00
17 | definition foofoo state bar equals foo
| ^^^
+ Test
Add test return codes Simply re-generated with 'make tests CLERK_OPTS=--reset'
2022-09-23 15:10:07 +03:00
#return code 255#
Register all existing tests through the new engine I removed the '.out' extension for now to preserve the test output file names and avoid a million file renames. This makes the patch easier to read, and we can do the rename easily in another patch afterwards, without mixing with semantic changes. (beautiful script àlarrache: ```bash for f in */*/output/*; do target_base=${f##*/} target_base=${target_base%%.*} echo $f | awk -F. '{ f=$1"."$2; if ($4 == "") { mode=$3; id=$3 } else { scope="-s "$3; mode=$4; id=$3"."$4} printf "\n```catala-test {id=\"%s\"}\ncatala %s %s\n```\n",id,mode,scope; }' >> $(dirname $f)/../${target_base}.*; done ```
2022-07-08 17:23:09 +03:00
```
Reference in New Issue Copy Permalink