Laurenz

For context, the current implementation comes from https://github.com/RazrFalcon/resvg/pull/769. This implementation was preceded by the earlier PR https://github.com/RazrFalcon/resvg/pull/754. The design in this PR is closer to #754 than #769. The discussion...

> The intention is that a wrapper type be used to manage that lock... which also requires an associated type (something I forgot to add previously)... > ... and thus...

Could you elaborate more on your motivation? The three bullet points from the original post all sound like conceptual concerns rather than motivating a specific use case that isn't currently...

For what it's worth, Typst also has its own font loading and metadata stack and its implementation of `FontSelectionFn` [can be found here.](https://github.com/typst/typst/blob/4e4c5175e531d99ec6f39d9a77d59d02f2109308/crates/typst/src/visualize/image/svg.rs#L46-L61) Might be interesting. Since the font selection...

Related: https://github.com/typst/typst/issues/6286

The thing that differs between the "Making a template" docs and your example is the part before the colon. In your case, there is no need to write `show table:`,...

> So in general to just set defaults, a set rule is the best bet and if additional logic is needed that is more complex that where() selectors, either special...

> Maybe these different behaviors of show should be assign to different keywords in the future. The bare `show:` actually used to be called `wrap`. But even though the implementation...

I'm not yet completely decided, but I'm open to discussing it. It should of course be restricted to the project/package directory like file loading. And there are further design decisions...

> As I'm still getting to know the ins and outs of Typst. Is the World trait the basic requirement used so that typst watch knows when to recompile the...