In Kusto, is there any difference in performance when using nested 'where' vs 'and'

Semantically these two queries are identical:

mytable
| where predicate1
| where predicate2

mytable
| where predicate1 and predicate2

Is there any difference performance-wise? Does the optimizer reduce #1 to #2 under the hood?