Flag `-nogc` does not guarantee that GC errors cannot happen

[kikofernandez]

Currently, someone can use the -nogc flag against the compiled binary to avoid some GC crashes (mainly due to not tracing correctly objects). This feature is not supposed to be used by anyone, but allow students to continue working on their implementation until we can provide GC fixes. However, there are some cases that are not covered by the -nogc flag and they should be addressed. As far as I know, futures may still crash even though you can pass the -nogc flag. There may be other cases.

[TheGrandmother]

Currently the -nogc flag only disables the garbage collection of passive objects (AFAIK) so issues related to the GCing of active objects does not disappear with the nogc flag.

[supercooldave]

In the future this will either need to be fixed or removed.