The inclusions of .errors makes Liquid::Template non thread-safe?

Hey All,

Since one of the core goals of liquid is to be a compilable resource, it would be assumed that one would use it something like this

# During application warmup
template = Liquid::Template.parse(something)

# And then, during runtime, in many different code paths
template.render({foo: "bar"})
template.render({foo: "baz})

However, since templates sets errors, this makes it inherently thread-unsafe. However, render! seems to be safer (all threads will set @rethrow_errors = true, and bubble up exceptions without any mutation)

Is this by design? Or am i doing something wrong?

Start by reading the behavior described around Liquid::Template.parse, template.render, render!, and the template errors state. Determine whether concurrent rendering can mutate shared errors, then document whether this is by design and what behavior would constitute a safe resolution.