24729, "bradcray", "[Performance]: 'stdout.getFile()' performs worse than '(new file(1))' in fasta", "2024-03-29T23:28:28Z"
While working on updating CLBG codes to Chapel 2.0, I came up with what I thought was the clever idea of replacing (new file(1)) expressions with stdout.getFile(), which felt far more comprehensible to the casual reader. Unfortunately, this change hurt fasta performance:
I was able to reproduce this on my Mac, just by changing that one expression back and forth. In the end, I just reverted the code since we'd already been using the similarly obscure openfd(1) expression in our last submitted version.
