Vladimir Gurevich

Hello @technobilly , I am sure it will be done at some point, but it takes time and effort. Since this is a free community project, I would encourage you...

In some well known implementations, they certainly are :) But the spec itself is not very specific.

@jafingerhut -- it might be useful to describe more specific goals and non-goals of the system. For example, I remember that we discussed it previously that the main goal was...

@jafingerhut Here are some of the typical things I expect would be needed for a reusable module, which mostly fall in the category of "amend something" or "fill in the...

@jafingerhut , I understand that this might be a lot, but that's precisely why I asked what is the desired use case :) I think that if we look at...

@jnfoster -- as I said, it would probably be easier if we define the scope explicitly, which is what prompted the discussion. Speaking of limiting the scope, splitting the code...

Did we intentionally forget about `|+|` and `|-|` operations? :)

Thanks a lot, @jafingerhut ! I hope this construct will promote using local metadata as much as possible, as opposed to the current model, where everything is global, partially due...

I thought, we discussed an option of distinguishing between: ``` header_t hdr1 = {}; // same as hdr1.setInvalid(); ``` and ``` header_t hdr1 = { ... }; // Same as...

We can agree that if someone wants to make an empty header valid, they should use `{...}` like on any other non-empty ones. Then `{}` will always mean invalid.