msg.data is a special environment constant that can only appear in certain contexts (like the argument to slice or to raw_call). It's not an ordinary env_item -- if it were treated as such it would be unclear what type to give it (since BytesT is always bounded, but msg.data is unbounded).
This issue is to figure out the right approach to add support for msg.data to our syntax and semantics. Maybe it can be added as an env item but with a fake type and usage restricted by the type system? Or maybe it should have special syntax (like how Pop is syntactically restricted to the places it can actually be used).
msg.datais a special environment constant that can only appear in certain contexts (like the argument tosliceor toraw_call). It's not an ordinaryenv_item-- if it were treated as such it would be unclear what type to give it (sinceBytesTis always bounded, butmsg.datais unbounded).This issue is to figure out the right approach to add support for
msg.datato our syntax and semantics. Maybe it can be added as an env item but with a fake type and usage restricted by the type system? Or maybe it should have special syntax (like howPopis syntactically restricted to the places it can actually be used).