vwithfield and ValueType.findWither
maurizio.cimadamore at oracle.com
Thu Jun 15 09:56:36 UTC 2017
On 15/06/17 10:47, John Rose wrote:
> My concern is for other kinds of code, outside the VCC, which uses
> compositions containing withers to build values, using MH's.
This seems to suggest something similar to where Paul was going, I think
- that is, findWither should _NOT_ be the vector for creating new DVT
from scratch. In other words, we have two use cases:
1) I want to make a new DVT
2) I want to tweak an existing DVT
I think it is fair to say that (1) should go through the POJO - as this
is an operation that is likely to occur at the 'boundaries' (outside of
the magic Q-MH world).
And if advanced clients need low level access to tweak DVT fields, they
can do so with a _real_ wither MH (not the mock one we expose now),
which maybe savior devs could access using privateLookupIn as Paul
What do you think?
More information about the valhalla-dev