Benjamin Bannier

> Does this match what spicy is doing? In general: not really. Typically Spicy parsers deal with data which arrives in chunks, e.g., for your example searching for `SMB` it...

One tricky aspect of this is that this could lead to users generating C++ files with optimizations while emitted prototypes would always be without optimizations. This could then expose different...

Unassigning myself since there is no capacity for this.

Closing this since we now have much more than initially planned with https://github.com/zeek/spicy-wireshark/. Let's discuss further work in dedicated issues there if needed.

The exception here occurs since `lahe` is inconsistent with the filtered view `Y` is operating on. Even when fixing that I cannot make this work as expected since the parser...

There are similar issues around `&parse-from` and likely `&parse-at` as well. They both set the input to a different stream which interferes with lookahead parsing. We should probably reject lookahead...

We should look into rejecting such code.

> To be fair, I don't think we ever aimed to support/be compatible with semantic versioning in any way > [..] > We also don't do versioning according to the...

This came up when writing Rust bindings for the websocket API. Rust's native floating point type [`f64`](https://doc.rust-lang.org/std/primitive.f64.html) is not [ordered](https://doc.rust-lang.org/std/cmp/trait.Ord.html), and cannot be compared for [equality](https://doc.rust-lang.org/std/cmp/trait.Eq.html) or [hashed](https://doc.rust-lang.org/std/hash/trait.Hash.html), so they...

> Just as a minor point: This would result in an error in parsing that's just "unexpected token" which seems unintuitive when it really looks like these attributes apply to...