Update PolyFuncType-vs-FunctionType docs, in rust+py, regenerate schema

hugr-py/src/hugr/serialization/tys.py

@@ -211,8 +211,8 @@ class Config:
 
 
 class PolyFuncType(BaseModel):
-    """A graph encoded as a value. It contains a concrete signature and a set of
-    required resources."""
+    """A polymorphic type scheme, i.e. of a FuncDecl, FuncDefn or OpDef.
+    (Nodes/operations in the Hugr are not polymorphic.)"""
 
     # The declared type parameters, i.e., these must be instantiated with the same
     # number of TypeArgs before the function can be called. This defines the indices
@@ -230,8 +230,8 @@ class Config:
         # Needed to avoid random '\n's in the pydantic description
         json_schema_extra = {
             "description": (
-                "A graph encoded as a value. It contains a concrete signature and "
-                "a set of required resources."
+                "A polymorphic type scheme, i.e. of a FuncDecl, FuncDefn or OpDef.  "
+                "(Nodes/operations in the Hugr are not polymorphic.)"
             )
         }
 

hugr/src/types/poly_func.rs

@@ -6,10 +6,11 @@ use itertools::Itertools;
 use super::type_param::{check_type_args, TypeArg, TypeParam};
 use super::{FunctionType, Substitution};
 
-/// A polymorphic function type, e.g. of a [Graph], or perhaps an [OpDef].
+/// A polymorphic type scheme, i.e. of a [FuncDecl], [FuncDefn] or [OpDef].
 /// (Nodes/operations in the Hugr are not polymorphic.)
 ///
-/// [Graph]: crate::ops::constant::Const::Function
+/// [FuncDecl]: crate::ops::module::FuncDecl
+/// [FuncDefn]: crate::ops::module::FuncDefn
 /// [OpDef]: crate::extension::OpDef
 #[derive(
     Clone, PartialEq, Debug, Default, Eq, derive_more::Display, serde::Serialize, serde::Deserialize,

hugr/src/types/signature.rs

@@ -11,8 +11,11 @@ use crate::extension::{ExtensionRegistry, ExtensionSet, SignatureError};
 use crate::{Direction, IncomingPort, OutgoingPort, Port};
 
 #[derive(Clone, Debug, Default, PartialEq, Eq, serde::Serialize, serde::Deserialize)]
-/// Describes the edges required to/from a node. This includes both the concept of "signature" in the spec,
+/// Describes the edges required to/from a node, and thus, also the type of a [Graph].
+/// This includes both the concept of "signature" in the spec,
 /// and also the target (value) of a call (static).
+///
+/// [Graph]: crate::ops::constant::Const::Function
 pub struct FunctionType {
     /// Value inputs of the function.
     pub input: TypeRow,

specification/hugr.md

@@ -1015,7 +1015,7 @@ However, for OpDef's, greater flexibility is allowed: each OpDef *either*
    `compute_signature` that fallibly computes a (perhaps-polymorphic) type scheme given some initial type arguments.
    The operation declares the arguments required by the `compute_signature` function as a list
    of TypeParams; if this successfully returns a type scheme, that may have additional TypeParams
-   for which TypeArgs must also be provided. 
+   for which TypeArgs must also be provided.
 
 For example, the TypeDef for `array` in the prelude declares two TypeParams: a `BoundedUSize`
 (the array length) and a `Type`. Any valid instantiation (e.g. `array<5, usize>`) is a type.

specification/schema/hugr_schema_v1.json

@@ -1018,7 +1018,7 @@
             "type": "object"
         },
         "PolyFuncType": {
-            "description": "A graph encoded as a value. It contains a concrete signature and a set of required resources.",
+            "description": "A polymorphic type scheme, i.e. of a FuncDecl, FuncDefn or OpDef.  (Nodes/operations in the Hugr are not polymorphic.)",
             "properties": {
                 "params": {
                     "items": {