Jordan Rome

> The first arg would have had to be a keyed map for it to have been a multi-delete. Why is that? This seems to work for me `BEGIN {...

> Maybe this needs to be done over a longer period of time to avoid changing the semantics under existing scripts. e.g. remove the multi-delete syntax in v0.22 and then...

> I just want to ensure that we don't support both multi-delete and the new syntax at the same time. If we immediately remove the multi-delete syntax that'd be fine...

Multi-delete was removed here: https://github.com/bpftrace/bpftrace/pull/3506

The idea of being able to assign to the args builtin is interesting. From the docs it seems `bpf_probe_write_user` is only valid for user-space threads and has the potential for...

Before this gets merged we need an email accessible to all the maintainers where people can report conduct violations. Or we can just have people make sure to email all...

@ajor Fortunately this is not a problem we have yet but as we grow I think it's a good to have this as a backstop should any bad behavior or...

Seems like there is general consensus to put something like this behind the `--unsafe` option. > I could see support landed in the form of a helper escape hatch. I...

Consolidating this issue, which is a duplicate, here: https://github.com/bpftrace/bpftrace/issues/28 The general feeling here is that we're not opposed to adding this feature (guarded by the `--unsafe` flag) but that it's...

Well it seems our current runtime tests are catching something 😄