Stack Exchange
open access
CC BY-SA
Shallow versus Deep Embeddings
When encoding a logic into a proof assistant such as Coq or Isabelle, a choice needs to be made between using a shallow and a deep embedding. In a shallow embedding logical formulas are written directly in the logic of the theorem prover, whereas in a deep embedding logical formulas are represented as a datatype. What are the advantages and limitations of the various approaches? Are there any guidelines available for determining which to use? Is it possible to switch between the two representations in any systematic fashion? As motivation, I would like to encode various security related logics into Coq and am wondering what the pros and cons of the different approaches are.
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- Can LLMs Use Relational Transformer Embeddings?#819903
- Beyond Sequence Order: Syntax-Informed Positional Embeddings for Transformers#432586
- On the Expressive Power and Limitations of Multi-Layer SSMs#924545
- On the Expressive Power and Limitations of Multi-Layer SSMs#920314
- Nested Regime Composition: Certified Interfaces, Obligation Flow, and the Soundness of Level Ascent#690950
Record · ID 787576
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive