In all the other languages I’ve worked with, el would be defined and would be the same as copy. Not in Liquid.

Of course, these are just the fixable “gotcha” type of issues. There are other things where it would be unfair to call it an issue. Arrays and objects are really intended to be mostly read-only in Liquid. So if you want to do multi-dimensional arrays in Liquid, you have to do some ugly gymnastics.

But to be fair, in that case you’re doing something that the language is actually designed to prevent. So that’s not a gotcha so much as attempting to do things the language is not really designed to do. It’s just a templating language, not a programming language.