Benoît Pasquier

I almost submitted the same issue a few hours ago, but for the out-of-place `update`, in which I would like to also be able to only update a few of...

Just throwing this a bit randomly as a follow-up on a discussion with @rafaqz: Thinking about a generic term to distinguish parameters that one may want to `collect` separately... What...

> If someone has a good syntax, please share. Pretty sure this is not the correct way of doing this (because a lot goes over my head), but did you...

Sorry for the word salad coming below, but another thing maybe of interest would be to be able to change the type (with the out-of-place `update`) of only those parameters...

No, sorry, not sure that I help... Would depending on Unitful for `using Unitful: NoUnits` be so bad though? I mean, I get that you want to keep the dependencies...

Oh that sounds great! I could definitely use a table to parameter function and vice versa! I'm not sure about the idea you suggested, I could not get it to...

Do I understand correctly that FieldDocTables is a tool to be used by other packages to display their FieldMetadata types in their documentation? Back to the table interface. Assuming I...

I get confused with these scopes... So when I do ```julia @metadata describe "" @describe mutable struct Described a::Int | "an Int with a description" b::Float64 | "a Float with...

Oh sorry no I meant the metadata —I messed up the code — I meant something more like ```julia julia> d = Described(1, 1.0) Described(1, 1.0) julia> t = table(d,...

BTW I should let you know that I have been doing this the otherway until now. That is, I first create a table and I create the struct from the...