3 ms·
Searching e.g. "xq31 curlyarrayconstructor does not use enclosedexpr": 1. In google, I get 9 results, none of which are a reference to the W3C XQuery/XPath iss
by rhdunn 3y ago
Searching e.g. "xq31 curlyarrayconstructor does not use enclosedexpr":
1. In google, I get 9 results, none of which are a reference to the W3C XQuery/XPath issue. This is because google is actually "helpfully" searching for "xq31 curly array constructor does not use enclosed expr" -- telling it to not do that finds the issue, returning two results.
2. In bing, the bug report (bug 29989) is the top result.
3. In DuckDuckGo, it is also the top result.
I've had other problems searching google for specific error messages as it decides to remove quoting, tends to show results for space-separated compound identifiers (see the "curly array constructor" in what google searches for by default), does word stemming, and other "helpful" transformations on the search.
- valicord 3y ago"I had to do an extra click on a clearly labeled link" does not equate "search engines are borderline useless"