mirror of
https://github.com/typst/typst
synced 2025-05-25 06:25:28 +08:00
Remove mentions that Typst makes specifically 5 attempts to stabilize (#2947)
This commit is contained in:
parent
d869a07d2d
commit
9024121905
@ -72,8 +72,8 @@ use crate::introspection::Location;
|
||||
/// titled `Real`. Thus, `count` is `1` and one `Fake` heading is generated.
|
||||
/// Typst sees that the query's result has changed and processes it again. This
|
||||
/// time, `count` is `2` and two `Fake` headings are generated. This goes on and
|
||||
/// on. As we can see, the output has five headings. This is because Typst
|
||||
/// simply gives up after five attempts.
|
||||
/// on. As we can see, the output has a finite amount of headings. This is
|
||||
/// because Typst simply gives up after a few attempts.
|
||||
///
|
||||
/// In general, you should try not to write queries that affect themselves. The
|
||||
/// same words of caution also apply to other introspection features like
|
||||
|
@ -170,8 +170,8 @@ use crate::World;
|
||||
/// a state, the results might never converge. The example below illustrates
|
||||
/// this. We initialize our state with `1` and then update it to its own final
|
||||
/// value plus 1. So it should be `2`, but then its final value is `2`, so it
|
||||
/// should be `3`, and so on. This example display `4` because Typst simply
|
||||
/// gives up after a few attempts.
|
||||
/// should be `3`, and so on. This example displays a finite value because
|
||||
/// Typst simply gives up after a few attempts.
|
||||
///
|
||||
/// ```example
|
||||
/// #let s = state("x", 1)
|
||||
|
Loading…
x
Reference in New Issue
Block a user