Documentation

Lean.Server.Rpc.Basic

Allows LSP clients to make Remote Procedure Calls to the server.

The single use case for these is to allow the infoview UI to refer to and manipulate heavy-weight objects residing on the server. It would be inefficient to serialize these into JSON and send over. For example, the client can format an Expr without transporting the whole Environment.

All RPC requests are relative to an open file and an RPC session for that file. The client must first connect to the session using $/lean/rpc/connect.

The address of an object in an RpcObjectStore that clients can refer to. Its JSON encoding depends on the RPC wire format.

The language server may serve the same RpcRef multiple times. It maintains a reference count to track how many times it has served the reference. If clients want to release the object associated with an RpcRef, they must release the reference as many times as they have received it from the server.

Instances For
    Equations
    Instances For
      @[implicit_reducible]
      Equations

      The RPC wire format specifies how user data is encoded in RPC requests.

      • v0 : RpcWireFormat

        Version 0 uses JSON. Serialized RPC data is stored directly in RpcCallParams.params and in JsonRpc.Response.result (as opposed to being wrapped in additional metadata). General types (except RPC references) are (de)serialized via ToJson/FromJson. RPC references are serialized as {"p": n}.

      • v1 : RpcWireFormat

        Version 1 is like 0, except that RPC references are serialized as {"__rpcref": n}.

      Instances For
        Equations
        • One or more equations did not get rendered due to their size.
        Instances For
          structure Lean.Server.WithRpcRef (α : Type u) :

          WithRpcRef α marks values that RPC clients should see as opaque references. This includes heavy objects such as Lean.Environments and non-serializable objects such as closures.

          In the Lean server, WithRpcRef α is a structure containing a value of type α and an associated id. In an RPC client (e.g. the infoview), it is an opaque reference. Thus, WithRpcRef α is cheap to transmit, but its data may only be accessed server-side. In practice, this is used by client code to pass data between various RPC methods provided by the server.

          Two WithRpcRefs with the same id will yield the same client-side reference.

          See also the docstring for RpcEncodable.

          • mk' :: (
          • )
          Instances For
            def Lean.Server.WithRpcRef.mk {α : Type} (val : α) :

            Creates an WithRpcRef instance with a unique id. As long as the client holds at least one reference to this WithRpcRef, serving it again will yield the same client-side reference. Thus, when used as React deps, client-side references can help preserve UI state across RPC requests.

            Equations
            Instances For
              Instances For
                Instances For
                  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
                      Equations
                      • One or more equations did not get rendered due to their size.
                      Instances For

                        RpcEncodable α means α can be used as an argument or return value in Remote Procedure Call (RPC) methods.

                        The following types are RpcEncodable by default:

                        • Any type with both FromJson and ToJson instances.
                        • Any type all of whose components (meaning the fields of a structure, or the arguments to inductive constructors) are RpcEncodable. Use deriving RpcEncodable to construct an instance in this case.
                        • Certain common containers, if containing RpcEncodable data (see instances below).
                        • Any WithRpcRef α where [TypeName α].

                        Some names are reserved for internal use and must not appear as the name of a field or constructor argument in any RpcEncodable type, or as an object key in any nested JSON. The following are currently reserved:

                        • __rpcref

                        It is also possible (but discouraged for non-experts) to implement custom RpcEncodable instances. These must respect the RpcObjectStore.wireFormat.

                        Instances
                          @[implicit_reducible]
                          Equations
                          @[implicit_reducible]
                          Equations
                          • One or more equations did not get rendered due to their size.
                          @[implicit_reducible]
                          Equations
                          • One or more equations did not get rendered due to their size.
                          @[implicit_reducible]
                          Equations
                          • One or more equations did not get rendered due to their size.
                          @[implicit_reducible]
                          Equations
                          • One or more equations did not get rendered due to their size.
                          @[implicit_reducible]
                          Equations
                          • One or more equations did not get rendered due to their size.
                          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