Improve documentation for field<T> function
Open
documentation
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 340
- PR merge metrics
- No merged PRs in 30d
Description
Improve the documentation for the `field` function, especially in regards to its behavior if the types mismatch.
From the review:
```
My
reading of this is that when you get the type wrong you are guaranteed
some kind of meaningful error report, and not just undefined behaviour;
is that right? Perhaps you should clarify.
```
##
Contributor guide
Assessment
This issue has not been assessed yet.