Laurenz

`sin` in particular also operates on angles, so that's something to consider. I like the clean approach of having things as methods, but the arguments in the [forge thread](https://discord.com/channels/1054443721975922748/1224715215615295510/1224997223973261444) against...

Based on all the discussion on Discord and the number of voices against it, I'll close this.

The web app has had spell check for a while now and for the CLI I consider it out of scope, so I'll close this.

Not sure what my thinking there was. Maybe I disabled it because I wanted to frequently highlight half-wrong things like `.foo(..)` in the docs and everything turned red all the...

Not sure whether we can easily adjust the comments there as it's reused on the code level.

I think the issue here differs from #311. If I'm understanding correctly, it's more that a bracket shouldn't disrupt the grid-like alignment of characters.

@Tom4sCruz I am currently in the process of refactoring the layout engine, so it's not an ideal time right now.

Another case are full page figures as requested in https://github.com/typst/typst/issues/4442.

There is already quite a bit of syntax sugar in the language for conveniently calling functions with trailing brackets. I think with this we have already exhausted our novelty budget...

The reason why I didn't make `smallcaps` an element function is that in contrast to `emph`, `strong`, `highlight`, etc. it isn't really a semantic thing to apply, but rather a...