Jordan Rome

Methods RFC: https://github.com/bpftrace/bpftrace/issues/3361 > I just meant it in the sense that while theoretically we can (and I'd say should!) deprecate and remove some things, in practice we've very rarely...

@jschwinger233 This is looking good as a start. > Do we want to support mixed use of named and positional arguments, like kstack(raw, limit=3)? Maybe eventually but I think as...

@jschwinger233 Thanks for the explanation. I think this is probably going to involve a bit more re-writing as we don't want this to be invalid `kstack(limit=1)`. Maybe this is a...

@jschwinger233 More or less. It’ll probably named something like CallPass and it should probably be run just before semantic analyser Perhaps the first PR in this process could be moving...

Ah good call. I forgot about the `map_sugar` pass. We can run this new pass before that one if needed. I think it would be good to support `delete(map=@a, mapkey=1)`...

Seems like this is resolved. Feel free to re-open

Perhaps another strategy would be to make bpftrace multi-threaded whereby it pulls items off the ring buffer as fast as it can and pushes these items into an async queue...

@amscanne I don't think I understand what this change is for.

Will functions in external c libraries also have this syntax available to them?

Should we add a script that can sync/update these and perhaps a bit in a readme