3 ms·

This isn't a compiler bug, and while the OP clearly did their due diligence, they make multiple statements in the blog post that are wrong, although they're on

• mort96 4y ago
  "It's never a compiler bug" is a reference to a commonly held idea that programmers are usually too quick to blame the compiler before realising the bug is actually in their own code. I chose to read the title to mean that the author _does_ know the difference between the compiler and the rest of the toolchain, but chose to let the slight inaccuracy slide for the sake of the reference. More interestingly, which other statements are wrong?
  • maccard 4y ago
    > but chose to let the slight inaccuracy slide for the sake of the reference. There's a _huge_ difference between a toolchain bug and a compiler bug. It's not really a slight inaccuracy. > More interestingly, which other statements are wrong? """I switched to the x64 version of VS Code and installed quick-lint-js from the VS Code Marketplace. The buggy squiggly appeared! I successfully reproduced the bug. Conclusion: The problem was specific to Windows x64 builds.""" The conclusion here is quite a stretch - the author has _not_ confirmed the problem is specific to x64 builds, they have confirmed they can repro it in x64 builds. The reason I call it out is because the author _is_ careful to differentiate between hypothesis and conclusion in the rest of the blog post, so this is either a copy error or a misunderstanding on their part!
    • strager 4y ago
      You're right. I should have written 'Hypothesis', not 'Conclusion', for that line. EDIT: I corrected the article. The statement is correct though. The bug was specific to Windows x64 builds when compiled with GCC-MinGW.