639 Matching Annotations
  1. Oct 2021
  2. Sep 2021
  3. Aug 2021
  4. Jul 2021
  5. Jun 2021
  6. May 2021
  7. Apr 2021
  8. Mar 2021
  9. Feb 2021
  10. Jan 2021
    1. I've reproduced, in a very simple way, what I would like it to do: https://svelte.dev/repl/2b0b7837e3ba44b5aba8d7e774094bb4?version=3.19.1

      This is the same URL as the original example given in issue description.

      I'm guessing what happened is they started with that one, made some changes, and then I think they must have forgot to save their modified REPL (which would have generated a new, unique URL).

  11. Dec 2020
  12. Nov 2020
  13. Oct 2020
    1. “"

      Which character is this referring to exactly?

      It looks like the empty string, which wouldn't make sense.

      https://www.postgresql.org/docs/13/functions-matching.html only lists these 2:

      If pattern does not contain percent signs or underscores, then the pattern only represents the string itself; in that case LIKE acts like the equals operator. An underscore (_) in pattern stands for (matches) any single character; a percent sign (%) matches any sequence of zero or more characters.

  14. Sep 2020
    1. Example 13.1 Estimate the grit channel length necessary if the maximum depth of flow in the channel is likely to be 1.7 m. Assume grit settling velocity = 10 cm/s, and horizontal flow velocity = 30 cm/s. Use scale-up factor = 5.0.

      I think the answer should be 25.5 m. Typo.

  15. Aug 2020
  16. Jul 2020
  17. Jun 2020
  18. May 2020
    1. foo?.bar!.baz;

      I think they meant:

      (foo?.bar)!.baz;

      because I think this is supposed to illustrate:

      Users who want to revert to the old behavior can add explicit parentheses around the left side of the ! operator.

  19. Apr 2020
    1. let page = document.getElementById('buttonDiv');

      duplication: As a result of duplication, they somehow ended with this line being present here but not in the downloadable file which is supposed to have the same contents as the snippet shown here.

      They should have updated their static page generation script/process so that their main document referenced options.js and their generator literally included the contents of the referenced file inline. Then there is no chance of the contents of the inline snippet and downloaded snippet diverging and not matching.

      Evidently, however, the contents of each are managed independently (in other words, there is duplication), easily leading to the contents diverging, as they did.

  20. Feb 2020
  21. Jan 2020
  22. Dec 2019
  23. Nov 2019
    1. ref={props.innerRef}

      Shouldn't this be ref={ref}? So that ref is actually used and the ref setter function in RefForm that sets refs actually gets passed the ref from the input?

  24. Sep 2019
  25. Aug 2019
  26. Jul 2019
  27. Jun 2019
  28. May 2019
  29. Apr 2019
  30. Mar 2019
  31. Feb 2019
  32. Jan 2019
  33. Dec 2018
  34. Nov 2018
    1. At left, an image with surface depth cues at 100% and interior depth cues at 50%. The image on the right has surface depth cues at 100% and interior depth cues at 50%.

      According to the description both images have surface depth cues at 100% and interior depth cues at 50%. It's clearly a typo.

  35. Oct 2018
  36. Sep 2018