REVIEW 2 cited by
On the Semantics of Intensionality and Intensional Recursion
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Intensionality is a phenomenon that occurs in logic and computation. In the most general sense, a function is intensional if it operates at a level finer than (extensional) equality. This is a familiar setting for computer scientists, who often study different programs or processes that are interchangeable, i.e. extensionally equal, even though they are not implemented in the same way, so intensionally distinct. Concomitant with intensionality is the phenomenon of intensional recursion, which refers to the ability of a program to have access to its own code. In computability theory, intensional recursion is enabled by Kleene's Second Recursion Theorem. This thesis is concerned with the crafting of a logical toolkit through which these phenomena can be studied. Our main contribution is a framework in which mathematical and computational constructions can be considered either extensionally, i.e. as abstract values, or intensionally, i.e. as fine-grained descriptions of their construction. Once this is achieved, it may be used to analyse intensional recursion.
Forward citations
Cited by 2 Pith papers
-
The gate of self-address: where decidable adjudication ends
A single self-referential query gate makes total correct adjudication impossible; bounding the depth keeps every finite level decidable, and full adjudication costs exactly one Turing jump.
-
G\"odel coding on fibrations and geminal categories
Defines code structures on fibrations to simplify the proof of Löb's theorem in geminal categories and adds a new categorical version of the Gödel-Löb axiom.
Discussion (0). Continue with ORCID to comment.