Yes, this is correct… you can’t search for it at all… if you try it here you get no results. Words that are likely to appear an extreme number of times (I, the, a, pronouns, etc) are excluded from indexing because they appear too often to provide meaningful differentiation.
same here, we and don't (technically don and t) are not indexed
this situation is a little different… for:
"just-use- interface{} / object ; we don't need generics"
that will never work, the quotes request an exact match and the spaces make it not an exact match
in the case of searching for:
"just-use-interface{}/object; we don't need generics"
the original post text contains a fancy quote (don’t) but search strips those out, so you can’t ever return an exact match for one… this means posts and search aren’t exactly symmetrical which is maybe something that could be improved
this is because without the quotes around it, you’re not searching for an exact match so it picks up the terms “interface” “object” “need” “generics” and that post is the best match for those terms
I found it very difficult to find the topics I was searching for, even with trivial words. It is something named before, and there was a Typesense integration experiment years ago.
I wonder if there are actual plans to improve the Discourse search function? It is one of the most featured tools, and I think it needs some refactoring and love.
Stop words are words that are very common, appear in almost every document, and have no discrimination value. Therefore, they can be ignored in the context of full text searching. For example, every English text contains words like a and the, so it is useless to store them in an index.