PgBiel

I made a small POC of having inheritance between Rust classes: https://github.com/PgBiel/gdext/commit/0f4131ca61e70b875a4ebd99582789a903412786 and https://github.com/PgBiel/gdext/commit/936dd1d67c0c353431117d2c36ae7df60bbfdd3e It worked and I could instantiate `Mob2` (which inherited from `Mob`) from within the editor (and...

Those are definitely important concerns; thanks for pointing them out. Regarding `Inherits` in particular, I gave a shot at this on my fork: https://github.com/PgBiel/gdext/commit/90cae572ea8f65d18b7e8ffb7d8222fe843d8802 In particular, we could try to...

> I think it would be better to add `table.row`, and use it for making each row separately, like > > ```typst > #table( > // ... > table.row[][], >...

> Tried to borrow some ideas from [Kotlin's type-safe builder](https://kotlinlang.org/docs/type-safe-builders.html) and I came up with this: > > -- snip -- > > The code behind it isn't that fancy,...

Regarding a dedicated syntax for tables: Personally, I think Markdown tables in particular are a bad fit for Typst, because they may require a good amount of fiddling to get...

Nice job! Looks good :smile: > I'm just not so sure about the possible limitations tho The main limitations I can think of are: 1. Lack of control over the...

> At this point, I think the best solution is to just downgrade it to a warning. I think this is a good use case for deny-by-default warnings - a...

> The whole thing is that people want to just keep writing before filling in their references. I'd argue that the compiler is right to be loud about this by...

> Otherwise you'll have to add preamble to every single subfile (chapters e.g.) to compile them stand-alone. I'm fine with that tradeoff. Using subfiles standalone is already problematic for any...

Re: https://github.com/typst/typst/pull/4974#issuecomment-2355791728 Cc @Enivex > I have the exact opposite impression. The majority would rather have references be a warning, without blocking compilation. I think arguing in terms of amount...