Jordan Rome

Notes from the office hours discussion about this: It seems like there was general consensus for this syntax: ``` type MyBpfScriptType = struct { name: string, stack: kstack_t, }; ```...

Sounds good to me. What do you think about shipping the tools and tools with the text files? Is it necessary to still have both? This also makes me want...

> Yeah that works too. Probably makes more sense - the tools are much more difficult to use without docs than bpftrace binary. I was asking if we should NOT...

Thanks @viktormalik. I thought I remembered you doing some work in this area.

Proposal sounds good to me and I like @danobi 's suggestion of not using ifdefs

@acj Awesome. Thanks! I'll put up a PR and give it a try.

Fixed here: - https://github.com/bpftrace/bpftrace/pull/4290

@Phoenix500526 Thanks for the write up. As long as there are no external breakages in terms of the user-facing API of bpftrace, we can change any of the internals. So...

@Phoenix500526 - @amscanne and I are working through some possible solutions to this problem. Codegen, as you mentioned, might be a possibility but we want to see if we can...

Thanks much @Phoenix500526 - This isn't a big rush but definitely something we want to complete in the next few months.