PgBiel

It is a bug because the compiler itself is crashing instead of printing an error. Note that the error you mention already exists: ```typ Error: cannot compare none and string...

> I want to make something like in [note-me](https://github.com/typst/packages/tree/main/packages/preview/note-me/0.1.1) package, but have the line with rounded ends How does it look like with the `radius` option? Maybe it's good enough...

Does the following work? ``` #tablex( columns: (auto, auto, auto, auto, auto), auto-vlines: false, hlinex(stroke: none), (), vlinex(), vlinex(), vlinex(), vlinex(), (), [a], [$u$], [$v$], [c], [d], hlinex(stroke: none) )...

Although I agree it'd be nice to be able to tell how far a certain line is from the end of the table when mapping it, so we can consider...

You can use `#set par.line(numbering: n => text(size: 6pt)[#n])`. `par.line` is a "virtual" element in the sense that it only exists for `#set par.line(numbering: ..., /* and other options */)`...

I intentionally left this out as I believed it could cause problems with header repetition, but I think I could add experimental support for this which just has the header...

I've made a more comprehensive fix which reimplements lists and enums using `terms`, which should also work on `width: auto` pages. Just paste the function code below and use `show:...

I've fixed symbol locations such that: 1. They now properly span the whole symbol, including a custom type's constructors or a function's body, so VSCode can now properly show the...

Included doc comments as part of the symbol ranges as well now. Seems to match the LSP spec's recommendation, as well as what `rust-analyzer` does (for comparison). 

By the way, let me know if I should have used `ast::visit` for any part of the implementation. In particular, I wanted to avoid introducing those more fine-grained location fields...