From b5604af62e671d652e848af64a52b6f62196d418 Mon Sep 17 00:00:00 2001 From: liamhuber Date: Sat, 4 Nov 2023 12:22:37 -0700 Subject: [PATCH] Update Channels docs --- pyiron_workflow/channels.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pyiron_workflow/channels.py b/pyiron_workflow/channels.py index c3003a42..f2901ad6 100644 --- a/pyiron_workflow/channels.py +++ b/pyiron_workflow/channels.py @@ -235,10 +235,10 @@ class DataChannel(Channel, ABC): (In the future they may optionally have a storage history limit.) (In the future they may optionally have an ontological type.) - Note that for the sake of computational efficiency, assignments to the `value` - property are not type-checked; type-checking occurs only for connections where both - channels have a type hint, and when a value is being copied from another channel - with the `copy_value` method. + Note that type checking is performed on value updates. This is typically not super + expensive, but once you have a workflow you're happy with, you may wish to + deactivate `strict_hints` throughout the workflow for the sake of computational + efficiency during production runs. When type checking channel connections, we insist that the output type hint be _as or more specific_ than the input type hint, to ensure that the input always