You know, we might consider this to be the same problem as we see here:

$ guile -L .
scheme@(guile-user)> (use-modules (foo))
;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
;;;       or pass the --no-autocompile argument to disable.
;;; compiling /tmp/foo.scm
;;; WARNING: compilation of /tmp/foo.scm failed:
;;; key read-error, throw args ("scm_i_lreadparen" "/tmp/foo.scm:3:1: end of file" () #f)
Throw to key `read-error':
ERROR: In procedure scm_i_lreadparen:
ERROR: /tmp/foo.scm:3:1: end of file
Entering the debugger. Type `bt' for a backtrace or `c' to continue.

1. debug> c

ERROR: In procedure scm_i_lreadparen:
ERROR: /tmp/foo.scm:3:1: end of file
scheme@(guile-user)> (use-modules (foo))
scheme@(guile-user)>

The second (use-modules (foo)) should not succeed.

Consider this example, where auto-compilation of (foo) fails:

#v+
$ cat foo.scm
(define-module (foo))
(open

$ cat bar.scm
(use-modules (foo))
(display "hello!\n")

$ guile -L . bar.scm
;;; note: source file bar.scm
;;;       newer than compiled /home/ludo/.cache/guile/ccache/2.0-0.R-LE-8/home/ludo/src/guile/bar.scm.go
;;; note: autocompilation is enabled, set GUILE_AUTO_COMPILE=0
;;;       or pass the --no-autocompile argument to disable.
;;; compiling bar.scm
;;; compiling ./foo.scm
;;; WARNING: compilation of ./foo.scm failed:
;;; key read-error, throw args ("scm_i_lreadparen" "./foo.scm:3:1: end of file" () #f)
;;; WARNING: compilation of bar.scm failed:
;;; key read-error, throw_args ("scm_i_lreadparen" "./foo.scm:3:1: end of file" () #f)
hello!

$ echo $?
0
#v-

Guile should instead abort as soon as auto-compilation fails.

Thanks,
Ludo'.