This repository has been archived by the owner on Jan 12, 2024. It is now read-only.
Move Exp
into libraries instead of intrinsics
#579
Labels
Kind-Enhancement
New feature or request
tracking
This label will trigger gh-sync to create or update a mirror internal ADO issue.
Move
Exp
into libraries instead of intrinsicsConceptual overview
Right now,
Exp
lives in theMicrosoft.Quantum.Intrinsic
namespace in part because of built-in decompositions for it in the native simulators. However, it is an advanced operation that does not map well to hardware intrinsics and requires advanced decomposition. Keeping it in the Intrinsic namespace is a little misleading, especially considering full support for it on hardware targets is challenging. We should deprecate the version inMicrosoft.Quantum.Intrinsic
in favor of a reasonable decomposition that lives in the libraries.Child issues
Exp
in qsharp-runtime: DeprecateExp
in favor of libraries implementation qsharp-runtime#999Microsoft.Quantum.Intrinsic
as fully supported APIs qsharp-runtime#1000Proposal
New and modified functions, operations, and UDTs
Exp
would be written in terms of decomposition of intrinsics and hosted in the libraries in an appropriate namespace.Exp
in the Intrinsic namespace would be deprecated. The new decomposition could make use of explicit two-qubit rotation gates that would be introduced in the Intrinsic namespace (see child issues).Open design questions and considerations
Exp
use two qubit rotation or decompose all the way into single qubit rotation gates? If two-qubit rotation is added to Intrinsics (possible itself decomposed), does it matter?The text was updated successfully, but these errors were encountered: