This comment has been minimized.

This may take a bit of work to fix -- this particular assert is easy to get rid of, but there are unfortunately a fair number of other places where the compiler forms symbol names by starting with "." and then tacking on the package path, which is problematic given the mangled type encoding machinery.