Currently, few of the quantumrt__* methods prescribe what should happen in case of an error. For example:
using a range with zero step,
getting an out of bounds element from an array,
projecting a 1D array,
concatenating non-1D arrays,
etc.
Leaving those cases unspecified means undefined behaviour, specific to each vendor implementation of the runtime. While it's a possible choice, it might be worth to consider being more prescriptive. And if we choose to go with UB, the spec should probably explicitly state so in the overview section.
Currently, few of the quantumrt__* methods prescribe what should happen in case of an error. For example:
Leaving those cases unspecified means undefined behaviour, specific to each vendor implementation of the runtime. While it's a possible choice, it might be worth to consider being more prescriptive. And if we choose to go with UB, the spec should probably explicitly state so in the overview section.