As mentioned in the article, it enables scenarios that getters/setters can't because of the borrow checker.

Ahh too bad, thanks for the answer though :)

Couldn't find any info, so maybe someone here knows: Is QT statically linkable, in particular when used from Rust? That's something that I really value in fltk.

Here's a blog post about the miscompilation bug: https://parsa.wtf/cast/

I've no idea. I kinda assume AI is basically used everywhere, but unless explicitely stated one can seldom be sure.

Wait, what? Any more details about this, I’ve never heard about that before. Partially run Drop impls sounds like a big potential for undefined behavior, how could catch_unwind possibly cause that?

Yeah, no, I don't think this is true. It's the reason a double panic will cause an abort. The docs do recommend against using this for general error recovery, but there's no mention of any possibillity of inconsistent state.

I don't have anything to add, except that typst is awesome. And that 'accessibler' should be a word.

I did fill out the survey. Turns out I don't have a usecase for any of this, and therefore I'm in the "don't care" realm really, since I'm also not really appreciative of corresponding features in other languages I know. I'd generally be critical of the cost vs. gain balance here though...