Fix handling of errors in imported modules (#387)

* Fix handling of errors in imported modules

- If a semantic error is detected in an imported module, then don't try to generate IR code for it

- Also, if a module (transitively) imports itself, then report that as an error
  - The way I'm checking for this is a bit hacky (I'm adding the module to the map of loaded modules, but in an "unfinished" state, and then using that unfinished state to detect the import of a module already being imported).

This isn't a 100% complete solution for any of the related problems, but it improves the user experience for the common case.

* Remove #import test.

The feature is slated to be removed, so it isn't worth fixing up this test case.

1 files changed, 11 insertions, 0 deletions

diff --git a/tests/bugs/import-with-error.slang b/tests/bugs/import-with-error.slang
new file mode 100644
index 000000000..f50bb1adb
--- /dev/null
+++ b/tests/bugs/import-with-error.slang
@@ -0,0 +1,11 @@
+//TEST:SIMPLE:-use-ir
+
+// Confirm that we correctly issue a diagnostic when
+// we `import` a module that has some errors in it.
+
+import import_with_error_extra;
+
+void main()
+{
+	broken();
+}