if let chain has a weird behaviour

[GuillaumeGomez]

I expected this code:

{%- if let Some(query) = search_query && !query.is_empty() %}

To either emit an error about the && after if let Some or to work, instead it generated:

if let Some(query,) = &(search_query && !self.query.is_empty()) {

Which is a very unexpected in-between.

I think it should generate if let Some(query) = search_query && !self.query.is_empty(). What do you think?

[djc]

I think it should generate if let Some(query) = search_query && !self.query.is_empty(). What do you think?

That certainly looks more sensible!

[GuillaumeGomez]

Another interesting bug coming from if let: the binding var (query in this case) is not recognized as such.