| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
The macro-generated code for `#[deftly(netdoc(flatten))]` relies on
this. The Default impl is genereated by the derive, but a generic
or handwritten `NetdocParseableFields` wouldn't work.
|
| |
|
|
| |
As a shorthand for T::intern_cache().intern(value).
|
| |
|
|
|
| |
This commit implements ItemValueParseable and ItemArgumentParseable for
Intern<T> types. This should be sufficient for the time being.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This allows implementing NormalItemArgument for types that can only be
parsed, or only displayed - or other combinations.
I noticed this restriction while inventing a type I later decided was
unnecessary. I still think it's a good change.
There is no practical impact elsewhere, since in practice downstream
code implements NormalItemArgument rather than relying on it.
|
| |
|
|
| |
When we can't parse a NormalItemArgument, that's Invalid, not Missing.
|
| | |
|
| |
|
|
|
| |
I keep not finding it because all the other signatures stuff is in
signatures.rs.
|
| |
|
|
| |
Roughly as per the proposal in `doc/dev/notes/authcert-in-consensus.md`.
|
| | |
|
| |
|
|
| |
We're going to have separate traits for encoding.
|
| |
|
|
| |
Once upon a time this trait handled multiplicity. But it doesn't any more.
|
| |
|
|
| |
This replaces one ad-hoc impl and will avoid having to have any more.
|
| | |
|
| | |
|
| |
|
|
|
| |
This will allow us to (1) move field name handling out of the argument
parser method, and also (2) add columns more easily.
|
| |
|
|
|
| |
This is currently used to enable `parse2::ItemArgumentParseable`.
In a moment it will enable `build::ItemArgument` too.
|
| |
|
|
| |
This will be useful for impls of ItemValueParseable.
|
| |
|
|
|
|
|
|
|
|
| |
Use the standard multiplicity technique rather than the ad-hoc impl on
Option. This allows us to support an ad-hoc parsing function for a
field that's `Option`.
Disentangle the `label` field attribute, which did both setting the
label, and expecting a different parsing approach: replace it with
`with`.
|
| | |
|
|
|
This isn't used anywhere yet. We're going to demonstrate it, and test
the demo, in a moment.
|