Fix backwards compatibility of dependency specification in textual language
* dep strings from textual language are not immediately split at the colon * the given string is tried to be matched with kernel query language * If not successful, it is treated as colon separated ID list (previous semantics) The only left-over problem is instruction IDs that match query tags. We could either black list them in instruction creation or live with it, your choice.
Loading
Please register or sign in to comment