Skip to content

Query handlers should be decoupled from Pyro aliases #388

@eb8680

Description

@eb8680

We currently use chirho.interventional.handlers.do and chirho.observational.handlers.condition in most user-facing code and documentation because they are drop-in replacements for pyro.do and pyro.condition respectively.

However, using do and condition in library code leads to some internal inconsistencies in API design and semantics that will be annoying to work around in the future. This issue tracks work on switching to using more idiomatic and consistently specified query handlers internally.

Tasks:

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions