Ayke van Laethem 3788b31ba5 main: add test for error coming from the optimizer ...

This is just one optimizer pass that's easy to test for. There are
others, but I'm ignoring them for now.

The one other that would be reasonable to test is when starting a
goroutine with -gc=none, but I'm leaving that one for another time.

2024-07-20 14:30:34 +02:00

..

importcycle

loader: handle go list errors inside TinyGo

2024-07-13 13:26:26 +02:00

invaliddep

loader: handle go list errors inside TinyGo

2024-07-13 13:26:26 +02:00

cgo.go

libclang: do not make error locations relative

2024-07-13 13:26:26 +02:00

compiler.go

main: add error tests for the compiler

2024-07-20 14:30:34 +02:00

interp.go

main: add interp tests

2024-07-20 14:30:34 +02:00

loader-importcycle.go

loader: handle go list errors inside TinyGo

2024-07-13 13:26:26 +02:00

loader-invaliddep.go

main: refactor error messages to use FileCheck-like patterns

2024-07-20 14:30:34 +02:00

loader-invalidpackage.go

loader: handle go list errors inside TinyGo

2024-07-13 13:26:26 +02:00

loader-nopackage.go

loader: handle go list errors inside TinyGo

2024-07-13 13:26:26 +02:00

optimizer.go

main: add test for error coming from the optimizer

2024-07-20 14:30:34 +02:00

syntax.go

all: add testing for compiler error messages

2024-07-13 13:26:26 +02:00

types.go

all: add testing for compiler error messages

2024-07-13 13:26:26 +02:00