Christian Vallentin

Ahh, yeah, you're right. For some reason I was confusing the short error with parser errors :)

> which is basically an "extend" but without an extra file What do you mean by "without an extra file"? Unless I'm misinterpreting something from the docs you linked, then...

I'm still not sure I understand the "without an extra file", maybe I'm tired, I don't know. :) If we go with your original example, you have a `page` template...

Yeah, I can follow that use case, I had something similar in mind. But I still don't _entirely_ understand how it would decrease the files needed? :) Ultimately isn't `concrete-modal.html`...

I'm not entirely up to date on this, but as far as I recall using e.g. `include_str!()` in an attribute is possible, but it is unstable and requires enabling the...

I don't have any thoughts or ideas beyond what's already discussed. :) I only have a minor comment: > [...] build script cannot modify/produce files anywhere outside of the folder...

What would the expected outcome be? That it propagates all the way up and returns an `Err` for [`render()`]? If yes, then there additionally, needs to be a way to...

We could make it optional. So if an `err = CustomError` or in the future an associated type is used, then `render()` uses that type. If it is not specified,...

It's not possible currently to call a macro like that, e.g. `{% call foo(call bar()) %}`. If the `icon` always results in `{% call icon::create(icon) %}`, then you can move...

I considered this issue while working on #396. I ended up not implicitly borrowing for let declarations. The reason being that it semantically mimics Rust more closure. I felt it...