Skip to content

Implement the RECONFIGURE modify path: reconfigure an existing input_signature #596

@khatchad

Description

@khatchad

Summary

#563 (#595) implemented the add-when-absent half of RECONFIGURE: a qualifying hybrid @tf.function that carries no input_signature gains the inferred one (passing precondition P4). The complementary modify path — reconfiguring a decorator that already supplies an input_signature — is deferred. This issue tracks it.

Current Behavior

When HybridizationParameters.hasInputSignatureParam() is true, check() does not select RECONFIGURE; the function falls through to HAS_NO_PRIMITIVE_PARAMETERS and is left unchanged. A user-supplied signature is never overwritten, per the presence/parse three-state contract from #557.

Goal

When a function already supplies an input_signature that disagrees with the inferred one, optionally rewrite it. The policy for when to overwrite versus preserve a user-supplied signature needs to be defined and is the substance of this work.

Design

Refs

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions