frozolotl
frozolotl
I would expect math mode to be consistent with code mode in that spaces and comments are not significant. At the moment, this is not the case. ## Examples `$foo.bar$`...
I will give a few code samples and how they are rendered at the time of writing. The part that is important for whether an element is part of a...
### Description The following code will give an error "unknown variable": ```typ let (fn-name)(arg) = arg #fn-name("a") ``` Removing the call to `fn-name` will cause the document to be accepted...
### Description The following code does not render anything and gives no error. ```typ #(: foo, bar) ``` The corresponding syntax tree: ``` Markup: 14 [ Hashtag: "#", Destructuring: 12...
### Description The compiler seems to get confused when parsing the following syntax: ```typ #(foo: _, bar: _, baz: _) ``` producing:  This issue is caused by `item` being...
### Description The following code is accepted by the compiler: ```typ #let foo((test: "bar")) = {} ``` To my knowledge, this function can't be called, without the compiler throwing an...
Supersedes #3364 and fixes #3312, as well as #2714.
In a markup context, a lone `]` without a `[` is not considered part of the surrounding object. This code is rendered like so: ```typst = [ x ] =...
I decided to use the word `shell` instead of turtle or tortoise because I think it is a bit clearer, the word reads nicer (“overshell” vs “overturtle”), and there is...