On Friday, 24 August 2018 at 01:57:03 UTC, Shachar Shemesh wrote:
At this point I can either use the work-around I already have
and (try to, obviously unsuccessfully) forget about it, file a
bug report that will be (justifiably) ignored because no-one
else can reproduce it, or spend an unknown amount of time (two
days would probably be low-balling at this point) in trying to
get this to reproduce on a watered down version of the code.
1. use the work-around, then
2. spend two man days, spread over two weeks 30-60 minutes at a
time, trying to reproduce on a watered down version of code ,
i.e. trying to isolate the problem
3. refactor once the real problem is found
from this nice article written by one of the better visionary
developer John Ousterhout
If you don't know what the problem was, you haven't fixed it
http://web.stanford.edu/~ouster/cgi-bin/sayings.php
