Skip to content
Snippets Groups Projects

DataUse.resolveDataType() ambiguous

    • Open Issue created by Martti Käärik @kaarik

    The semantics of resolveDataType() operation is currently ambiguous as the specification doesn't say if the reduction is taken into account or not. The usage of the operation in constraints implies different meanings (sometimes with reduction other times without).

    Example 1: "Type of a 'memberSpec' shall conform to the type of the 'member'" constraint expression assumes that resolveDataType() provides the type resolved after applying the reduction.

    Example 2: "Structured data types in 'reduction' set" constraint expression assumes that resolveDataType() provides the base type.

    Solution:

    1. Specify additional operation (for the second case) to distinguish between the two.
    2. Update the implementation of the resolveDataType() operation to return the type after the reduction is resolved.
    Edited
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    Please register or sign in to reply