> In this case, though... It seems only 1 person has experienced this, and didn't care enough to even reply back. Closing it due to inactivity doesn't seem to be wrong, to me.

The blog post linked to two other reports of the same issue (all closed or ignored), and the author mentioned that he himself had run into it prior to turning up these abandoned reports on their bug-tracker.

And really, given the egregiousness of the symbol exporting issue, it would be nearly impossible for only one person to have run into it.