You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current behavior is to stop analyzing a single file if an exception is thrown, but to go on and try to analyze other namespaces. However, when an exception is thrown on one namespace, no further analysis and eval is done for any later forms in the file. Thus if there are Vars defined later in that file with the first exception, it can cause undefined Var exceptions during analysis of later namespaces that assume that Var is defined, which is misleading.
It still might be useful for my own development testing to have an option to operate as it currently does, because then output from one crucible run to the next might be more consistent.
The text was updated successfully, but these errors were encountered:
The current behavior is to stop analyzing a single file if an exception is thrown, but to go on and try to analyze other namespaces. However, when an exception is thrown on one namespace, no further analysis and eval is done for any later forms in the file. Thus if there are Vars defined later in that file with the first exception, it can cause undefined Var exceptions during analysis of later namespaces that assume that Var is defined, which is misleading.
It still might be useful for my own development testing to have an option to operate as it currently does, because then output from one crucible run to the next might be more consistent.
The text was updated successfully, but these errors were encountered: