Optimize variable flatteningvalentindavid/optimize-variables

Verifying for variables (all used variables defined and no cycle) is
much faster than flattening them. It also uses much less memory.  Only
`bst show -f "%{vars}"` requires to flatten all variables.  For other
cases we can improve performance by only checking rather than
flattening.

Also flattening very nested variables could lead to very long lists of
empty strings. The memory usage for flattening could be a lot bigger
than the resulting value. Force flattening and caching every
variable definitions can improve intermediate memory consumption and
only consume memory of the size of the result.

Finally, an optimization allowed inifinite cycles leading to
segmentation fault. This was solved by simplifying the code.

1 files changed, 9 insertions, 0 deletions

diff --git a/tests/format/variables.py b/tests/format/variables.py
index 616dc20c1..c5e8eebad 100644
--- a/tests/format/variables.py
+++ b/tests/format/variables.py
@@ -63,6 +63,15 @@ def test_missing_variable(cli, datafiles, element):
 
 @pytest.mark.timeout(15, method="signal")
 @pytest.mark.datafiles(os.path.join(DATA_DIR, "cyclic_variables"))
+def test_simple_cyclic_variables(cli, datafiles):
+    print_warning("Performing cyclic test, if this test times out it will " + "exit the test sequence")
+    project = str(datafiles)
+    result = cli.run(project=project, silent=True, args=["build", "simple-cyclic.bst"])
+    result.assert_main_error(ErrorDomain.LOAD, LoadErrorReason.RECURSIVE_VARIABLE)
+
+
+@pytest.mark.timeout(15, method="signal")
+@pytest.mark.datafiles(os.path.join(DATA_DIR, "cyclic_variables"))
 def test_cyclic_variables(cli, datafiles):
     print_warning("Performing cyclic test, if this test times out it will " + "exit the test sequence")
     project = str(datafiles)