The overloaded binary && operator can be used to combine queries together. When the queries to be combined
don’t have any unary operators applied to them, the resulting query is a bool query with must clauses

As per the previous example, NEST will combine multiple should or || into a single bool query
with should clauses, when it sees that the bool queries in play only consist of should clauses;

To summarize, this

term || term || term

becomes

bool
|___should
|___term
|___term
|___term

However, the bool query does not quite follow the same boolean logic you expect from a
programming language. That is

term1 && (term2 || term3 || term4)

does not become

bool
|___must
| |___term1
|
|___should
|___term2
|___term3
|___term4

Why is this? Well, when a bool query has onlyshould clauses, at least one of them must match.
However, when that bool query also has a must clause, the should clauses instead now act as a
boost factor, meaning none of them have to match but if they do, the relevancy score for that document
will be boosted and thus appear higher in the results. The semantics for how should clauses behave then
changes based on the presence of the must clause.

So, relating this back to the previous example, you could get back results that only contain term1.
This is clearly not what was intended when using operator overloading.

if NEST identified both sides of a binary || operation as only containing should clauses and
joined them together, it would give a different meaning to the minimum_should_match parameter of
the first bool query; rewriting this to a single bool with 5 should clauses would break the semantics
of the original query because only matching on term5 or term6 should still be a hit.

If you assigning many bool queries prior to NEST 2.4.6 into a bigger bool query using an assignment loop,
the client did not do a good job of flattening the result in the most optimal way and could
cause a stackoverflow when doing ~2000 iterations. This only applied to bitwise assigning many bool queries,
other queries were not affected.