You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#5323 provided a quick solution for the problem of passing the same value to several different arguments.
The downsides are that it's actually an extra call that we will have to carry on in our reproducers and that puts extra burden on our resource generation/mutation code.
I wonder if we can reimplement in a cleaner way, e.g. by introducing some resource values like:
value x[int16[0:10]]
value y[int16]: 2, 4, 8, 16
which will act like resources (and which would be represented exactly like resources: using *prog.ResourceType, *prog.ResourceDesc, *prog.ResultArg), but they won't require any extra pseudo syscalls and we won't be able to return them from fuctions.
#5323 provided a quick solution for the problem of passing the same value to several different arguments.
The downsides are that it's actually an extra call that we will have to carry on in our reproducers and that puts extra burden on our resource generation/mutation code.
I wonder if we can reimplement in a cleaner way, e.g. by introducing some resource values like:
which will act like resources (and which would be represented exactly like resources: using
*prog.ResourceType
,*prog.ResourceDesc
,*prog.ResultArg
), but they won't require any extra pseudo syscalls and we won't be able to return them from fuctions.There can also be some synergy with #1621
The text was updated successfully, but these errors were encountered: