Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The bifcl parser doesn't understand compound types very well #14

Open
ckreibich opened this issue Sep 1, 2022 · 1 comment
Open

The bifcl parser doesn't understand compound types very well #14

ckreibich opened this issue Sep 1, 2022 · 1 comment

Comments

@ckreibich
Copy link
Member

builtin-func.y has a couple of TODOs that have been around for a long time. For example, the type rule has this comment:

// TODO: Migrate all other compound types to this rule. Once the BiF language
// can parse all regular Zeek types, we can throw out the unnecessary
// boilerplate typedefs for addr_set, string_set, etc.

For example, this means that a BiF can return a type alias that's a vector of foo, but the function cannot itself return vector of foo.

@timwoj
Copy link
Member

timwoj commented Sep 2, 2022

Maybe related: zeek/zeek#1472

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants