Bruno Le Floch

I think `\tl_case:Nn` should be removed or renamed `\cs_case_meaning:Nn`. It is a leftover from the old days where one had to compare macros with stored values to get any reasonable...

We concluded \tl_case:Nn should be deprecated and renamed \cs_case_meaning:Nn, but there is already \token_case_meaning:Nn, which seems to fit the bill. Relatedly, `\tl_if_eq:NN(TF)`, `\cs_if_eq:NN(TF)` and `\token_if_eq_meaning:NN(TF)` have identical definitions, and probably...

> \file_input:nnn {code.tex} {\ExplSyntaxOff} {\ExplSyntaxOn} Sorry, I should've been clearer. The issue is not about how to go back to ExplSyntaxOn, but about *whether* to go back: these packages test...

I suspect `\xspace` should have two exception lists, one for characters tested with `\if\expandafter\noexpand\csname @let@token\endcsname\noexpand#1` and one for control sequences or active characters, tested with `\expandafter\ifx\csname @let@token\endcsname#1`. But perhaps something...

I think it is a good idea. The main question is what name would be reasonable for this variable.

The problem comes when your figure is called `plain`, or some other pretty reasonable name that just happens to collide with an unrelated system file. Then kpsewhich will find the...

I suspect that there are almost no uses of \use:c that could not be replaced by a checking-for-existence \cs_use:c, or by \exp_not:c. So we could imagine deprecating \use:c.

I agree the name doesn't read well. I was modelling it after `\tl_if_in:nnTF` or `\clist_if_in:nnTF` where the list comes first. Another question is my choice of "empty means infinity", and...

I think the combination of your comments suggests we should actually provide a new `intset` datatype (and `fpset`) to keep track of subsets of the integers, so \intset_new:N \g_small_primes_intset \intset_gset:Nn...

For reference this was already proposed in #24 and closed (nothing much to gather from that issue). `\intset_gremove` is O(N M) naively for a sets of N and M ranges...