- strict: {α β : Type} → α → Lean.Widget.StrictOrLazy α β
- lazy: {α β : Type} → β → Lean.Widget.StrictOrLazy α β
Instances For
Equations
- Lean.Widget.instInhabitedStrictOrLazy = { default := Lean.Widget.StrictOrLazy.strict default }
Equations
- Lean.Widget.instRpcEncodableStrictOrLazy = { rpcEncode := Lean.Widget.instRpcEncodableStrictOrLazy.enc✝, rpcDecode := Lean.Widget.instRpcEncodableStrictOrLazy.dec✝ }
- indent : Nat
- children : Array (Lean.Server.WithRpcRef Lean.MessageData)
Instances For
- expr: Lean.Widget.CodeWithInfos → Lean.Widget.MsgEmbed
A piece of Lean code with elaboration/typing data. Note: does not necessarily correspond to an
Expr
, the name is for RPC API compatibility. - goal: Lean.Widget.InteractiveGoal → Lean.Widget.MsgEmbed
An interactive goal display.
- trace: Nat →
Lake.Name →
Lean.Widget.TaggedText Lean.Widget.MsgEmbed →
Bool →
Lean.Widget.StrictOrLazy (Array (Lean.Widget.TaggedText Lean.Widget.MsgEmbed))
(Lean.Server.WithRpcRef Lean.Widget.LazyTraceChildren) →
Lean.Widget.MsgEmbed
Some messages (in particular, traces) are too costly to print eagerly. Instead, we allow the user to expand sub-traces interactively.
Instances For
Equations
- Lean.Widget.instInhabitedMsgEmbed = { default := Lean.Widget.MsgEmbed.expr default }
Equations
- Lean.Widget.instRpcEncodableMsgEmbed = { rpcEncode := Lean.Widget.instRpcEncodableMsgEmbed.enc✝, rpcDecode := Lean.Widget.instRpcEncodableMsgEmbed.dec✝ }
The message
field is the text of a message possibly containing interactive embeds of type
MsgEmbed
. We maintain the invariant that embeds are stored in .tag
s with empty .text
subtrees,
i.e. .tag embed (.text "")
, because a MsgEmbed
display involve more than just text.
Equations
Instances For
Equations
- Lean.Widget.instRpcEncodableDiagnosticWith = { rpcEncode := Lean.Widget.instRpcEncodableDiagnosticWith.enc✝, rpcDecode := Lean.Widget.instRpcEncodableDiagnosticWith.dec✝ }
Equations
- One or more equations did not get rendered due to their size.
Instances For
Equations
- One or more equations did not get rendered due to their size.
Instances For
The msgToInteractive
algorithm turns a MessageData
into TaggedText MsgEmbed
in two stages.
First, in msgToInteractiveAux
we produce a Format
object whose .tag
nodes refer to EmbedFmt
objects stored in an auxiliary array. Only the most shallow .tag
in every branch through the
Format
corresponds to an EmbedFmt
. The kind of this tag determines how the nested Format
object (possibly including further .tag
s), is processed. For example, if the output is
.tag (.expr ctx infos) fmt
then tags in the nested fmt
object refer to elements of infos
.
In the second stage, we recursively transform such a Format
into TaggedText MsgEmbed
according
to the rule above by first pretty-printing it and then grabbing data referenced by the tags from
all the nested arrays (such as the infos
array in the example above).
We cannot easily do the translation in a single MessageData → TaggedText MsgEmbed
step because
that would effectively require reimplementing the (stateful, to keep track of indentation)
Format.prettyM
algorithm.
Equations
- Lean.Widget.instInhabitedEmbedFmt = { default := Lean.Widget.EmbedFmt.trace default default default default }
Equations
- One or more equations did not get rendered due to their size.
Instances For
Transform a Lean Message concerning the given text into an LSP Diagnostic.
Equations
- One or more equations did not get rendered due to their size.