Merge pull request #1135 from aiken-lang/fix_bytearray_comments
fix bytearray comments
fix bytearray comments
inside of UntypedExpr::ByteArray and UntypedPattern::ByteArray
Signed-off-by: KtorZ <[email protected]>
Signed-off-by: KtorZ <[email protected]>
rework trace label evaluation strategy
Provide better errors when failing to match validators in blueprint apply.
Signed-off-by: KtorZ <[email protected]>
Allow captures within constructor calls.
Compiler said I couldn't do it, so I changed the compiler. Signed-off-by: KtorZ <[email protected]>
Namely: 1. Fully evaluate & type-check the label, irrespective of the trace level. So that labels using other variables do not generate "unused identifier" warnings when compiling with different trace mode (and so that the success of a build doesn't depend on the trace level). This was already done for trace arguments, but not for labels, somehow. 2. Move the requirement for compact trace label being String from errors down to warnings; following point (1), we shouldn't fail compilation for different trace levels. It seems more reasonable to simply raise a warning. Signed-off-by: KtorZ <[email protected]>
Namely: 1. Fully evaluate & type-check the label, irrespective of the trace level. So that labels using other variables do not generate "unused identifier" warnings when compiling with different trace mode (and so that the success of a build doesn't depend on the trace level). This was already done for trace arguments, but not for labels, somehow. 2. Move the requirement for compact trace label being String from errors down to warnings; following point (1), we shouldn't fail compilation for different trace levels. It seems more reasonable to simply raise a warning. Signed-off-by: KtorZ <[email protected]>