`ZInterCard` && `SInterCard` should use the optional `limit` argument.

[infdahai]

I find the limit argument is optional in sintercard page and the same as zintercard.

I see #2291 and #2345 but it seems we don't consider the situation.

[SoulPancake]

@monkey92t Any specific reason we don't respect the limit being optional? We have done a similar thing regarding ACL LOG where we always take count as an arg as well.

[monkey92t]

cp from redis.doc:

By default, the command calculates the cardinality of the intersection of all given sets. When provided with the optional LIMIT argument (which defaults to 0 and means unlimited), if the intersection cardinality reaches limit partway through the computation, the algorithm will exit and yield limit as the cardinality. Such implementation ensures a significant speedup for queries where the limit is lower than the actual intersection cardinality.

[monkey92t]

so...

SINTERCARD 2 k1 k2 == SINTERCARD 2 k1 k2 LIMIT 0

[infdahai]

So this situation is to make an equivalent.

[monkey92t]

The omission or inclusion of such optional parameters doesn't make a significant difference.

We do not ignore optional parameters that have a specific meaning....
For example, SET key value != SET key value NX.

[infdahai]

I get it.