Skip to content

a bunch of methods acting on abstract types assume internal layout for these types #12

@Krastanov

Description

@Krastanov

E.g.:

Long term, a better design would be to move these to QuantumOpticsBase where they will act on concrete (not abstract) types (this is where they came from). Methods acting on abstract types should use only public APIs, not assumptions about internal layout, because the internal layout might be different in other libraries extending this functionality. E.g. QuantumClifford.PauliChannel superoperators do not have basis_l slots, unlike QuantumOptics superoperators.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions