notes from Valhalla meeting 5/24/17
paul.sandoz at oracle.com
Wed Jun 21 23:59:59 UTC 2017
> On 21 Jun 2017, at 16:49, John Rose <john.r.rose at oracle.com> wrote:
> On Jun 21, 2017, at 4:44 PM, Paul Sandoz <paul.sandoz at oracle.com <mailto:paul.sandoz at oracle.com>> wrote:
>> A BSM called to resolve a constant can choose when pulling it’s static args to catch and swallow linkage exceptions, keep on trucking, and return a value. Should this be allowed?
> Absolutely. The BSM might have an API-specific fallback.
Thanks, i thought so.
The returned value could capture the ConstantGroup and do more resolution lazily on demand. At some point if the value is tickled in the right way a linkage error might result.
> I'm also thinking that we could add a query for the original symbolic reference,
> which the BSM could look and and perhaps resolve "by hand".
> This is similar in spirit to the original "invokedynamic" proposals
> as a form of "messageNotUnderstood".
> — John
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the valhalla-spec-experts