> On 21 Jun 2017, at 16:49, John Rose <john.r.r...@oracle.com> wrote: > > On Jun 21, 2017, at 4:44 PM, Paul Sandoz <paul.san...@oracle.com > <mailto:paul.san...@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. Paul. > 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
