Add no_std feature?

[Kijewski]

I think the generated code can easily be #![no_std]. We only need std to impl std::error::Error for rinja::Error. We need alloc for a few filters. Both use cases can be feature-gated. Then I think, we can add the features ↓ and be useful to a marginally wider audience.

default = […, "std"]
std = ["alloc"]
alloc = []

What do you think?

[GuillaumeGomez]

Hum... Do you know any project where it could be useful? Because unless there is one, I'm not sure if it's worth it (even though it'd likely be a very small amount of code). I'm not against it, just not convinced.

[Kijewski]

No, spontaneously I cannot come up with a use cases. Probably there isn't one. I guess there won't be many IoT device developers who need a template engine. :)

[GuillaumeGomez]

Who knows? World is a surprising place.

[dodomorandi]

We only need std to impl std::error::Error for rinja::Error.

Just in case you decide to have a MSRV 1.81: rust-lang/rust#103765

[GuillaumeGomez]

Oh nice, thanks for the information!