cqlib-core 0.1.0-beta.7

The high-performance core foundation for the CQLib quantum computing ecosystem.
Documentation
// This code is part of Cqlib.
//
// (C) Copyright China Telecom Quantum Group 2026
//
// This code is licensed under the Apache License, Version 2.0. You may
// obtain a copy of this license in the LICENSE.txt file in the root directory
// of this source tree or at http://www.apache.org/licenses/LICENSE-2.0.
//
// Any modifications or derivative works of this code must retain this
// copyright notice, and modified files need to carry a notice indicating
// that they have been altered from the originals.

//! # Quantum Device Module
//!
//! This module provides types for modeling quantum hardware devices.
//! It includes device topology, qubit layout mapping, noise models,
//! and execution result handling.
//!
//! ## Key Components
//!
//! - [`Device`]: Quantum device specification with qubit and edge properties
//! - [`Topology`]: Device connectivity graph
//! - [`Layout`]: Logical to physical qubit mapping
//! - [`NoiseModel`]: Noise simulation parameters
//! - [`ExecutionResult`]: Measurement outcome collection
//!
//! ## Instruction capability semantics
//!
//! [`Topology`] describes directed physical connectivity only; a coupling edge
//! does not by itself name the instructions executable on that edge.
//! [`Device::native_gates`] is the device-wide default capability set. A qubit
//! or directed edge with no local native instructions inherits the matching
//! one- or two-qubit defaults. A non-empty local native-instruction list is a
//! complete override for that physical location.
//!
//! Local capabilities are never synchronized back into the device defaults,
//! and replacing the defaults does not remove local capabilities. Two-qubit
//! capabilities are ordered: support on `(control, target)` does not imply
//! support on `(target, control)`. Calibration data describes a supported
//! instruction but does not create support for an otherwise unsupported one.
//!
//! Native capability writers validate their inputs and return [`DeviceError`].
//! Device defaults accept standard gates acting on at most two qubits, while
//! qubit and edge properties accept exactly one- and two-qubit standard gates,
//! respectively. Validation completes before mutation, so a rejected update
//! preserves the previous capability set.

pub mod device_impl;
pub mod error;
pub mod layout;
pub mod noise;
pub mod qubit;
pub mod result;
pub mod topology;

pub use device_impl::{Device, EdgeProp, InstructionProp, QubitProp};
pub use error::{DeviceError, DeviceValidationError, LayoutError, TopologyError};
pub use layout::Layout;
pub use noise::{NoiseModel, OperationKey, ReadoutError, SingleQubitNoise, TwoQubitNoise};
pub use qubit::{LogicalQubit, PhysicalQubit};
pub use result::{ExecutionResult, Outcome, Status};
pub use topology::Topology;