Remove expect-fx syntax and handling

This was never fully hooked up in platforms, and the plan is to replace the need for this with doing purity-inference on normal `expect` statements.

On the other hand, fuzzing is finding some bugs caused by having a hyphenated keyword, so this is a great time to go ahead and remove it!
This commit is contained in:
Joshua Warner 2024-11-17 20:24:09 -08:00
parent 7bf3701c9e
commit 9ead801536
No known key found for this signature in database
GPG key ID: 89AD497003F93FDD
32 changed files with 21 additions and 641 deletions

View file

@ -1,39 +0,0 @@
Defs {
tags: [
EitherIndex(2147483648),
],
regions: [
@25-41,
],
space_before: [
Slice { start: 0, length: 1 },
],
space_after: [
Slice { start: 1, length: 1 },
],
spaces: [
LineComment(
" expecting some effects",
),
Newline,
],
type_defs: [],
value_defs: [
ExpectFx {
condition: @35-41 BinOps(
[
(
@35-36 Num(
"5",
),
@37-39 Equals,
),
],
@40-41 Num(
"2",
),
),
preceding_comment: @0-24,
},
],
}

View file

@ -1,2 +0,0 @@
# expecting some effects
expect-fx 5 == 2

View file

@ -333,7 +333,6 @@ mod test_snapshots {
pass/equals_with_spaces.expr,
pass/expect.expr,
pass/expect_defs.moduledefs,
pass/expect_fx.moduledefs,
pass/expect_single_line.expr,
pass/extra_newline.expr,
pass/extra_newline_in_parens.expr,