On Wed, Dec 9, 2020 at 2:29 PM Vern Paxson <v...@corelight.com> wrote:
> It already varies with type of variable for assignments and function > call parameters. Thus I’m puzzled at the desire for deep-copy over > shallow-copy, given that Zeek is already primarily shallow-copy. Same for me: wondering what's actually (in)consistent given the behavior of assignment/call-params. Otherwise, I don't have a strong opinion about what the lambda semantics should be, but if a change does occur, the one thing that's for sure on my wishlist is consideration for some deprecation-path, differentiating-syntax (maybe event just temporary), or other warning/notice that can help users along instead of potentially breaking their code outright. - Jon _______________________________________________ zeek-dev mailing list -- zeek-dev@lists.zeek.org To unsubscribe send an email to zeek-dev-le...@lists.zeek.org
