{"route":"/en-US-v0.14.1/reference/foundations/std/","title":"Standard Library","description":"Documentation for the std functions.","part":null,"outline":[{"id":"summary","name":"Summary","children":[]},{"id":"using-shadowed-definitions","name":"Using \"shadowed\" definitions","children":[]},{"id":"conditional-access","name":"Conditional access","children":[]},{"id":"functions","name":"Functions","children":[]}],"body":{"kind":"group","content":{"name":"std","title":"Standard Library","details":"

A module that contains all globally accessible items.

\n

Using "shadowed" definitions

\n

The std module is useful whenever you overrode a name from the global\nscope (this is called shadowing). For instance, you might have used the\nname text for a parameter. To still access the text element, write\nstd.text.

\n
#let par = [My special paragraph.]\n#let special(text) = {\n  set std.text(style: "italic")\n  set std.par.line(numbering: "1")\n  text\n}\n\n#special(par)\n\n#lorem(10)\n
\"Preview\"
\n

Conditional access

\n

You can also use this in combination with the dictionary\nconstructor to conditionally access global definitions. This\ncan, for instance, be useful to use new or experimental functionality when\nit is available, while falling back to an alternative implementation if\nused on an older Typst version. In particular, this allows us to create\npolyfills.

\n

This can be as simple as creating an alias to prevent warning messages, for\nexample, conditionally using pattern in Typst version 0.12, but using\ntiling in newer versions. Since the parameters accepted by the tiling\nfunction match those of the older pattern function, using the tiling\nfunction when available and falling back to pattern otherwise will unify\nthe usage across all versions. Note that, when creating a polyfill,\nsys.version can also be very useful.

\n
#let tiling = if "tiling" in std { tiling } else { pattern }\n\n...\n
","functions":[],"global_attributes":[]}}}