From: Per Bothner <per@bothner.com>
To: Phil Eaton <phil@eatonphil.com>
Cc: spellcard199 <spellcard199@protonmail.com>,
kawa mailing list <kawa@sourceware.org>
Subject: Re: Receiver class does not define or inherit an implementation of the resolved method
Date: Tue, 7 Sep 2021 13:13:07 -0700 [thread overview]
Message-ID: <ee223b16-fb46-995e-d092-6e7026672a7b@bothner.com> (raw)
In-Reply-To: <CAByiw+opaCbWSaPGe_cST4j7H9N+ZKff7Qj_Ht3Dp5rw18EHeg@mail.gmail.com>
On 9/7/21 12:45 PM, Phil Eaton wrote:
> I did do a bunch of grepping but it hadn't turned up yet. Since that gnu/expr/LambdaExp.java code is adding a literal $X I don't think that's what I'm looking for.
I think the code that renames duplicate methods is in LambdaExp.java
around line 1156,
Looking more, it looks like Kawa does support co-variant return types.
(Kawa is so big and so old I don't remember everything in it ...)
See generateBridgeMethod in ClassExp.java.
It seems to me you can either have:
((apply (ctx ::io.jooby.Context)) ::string ...)
or:
((apply (ctx ::io.jooby.Context)) ::java.lang.Object ...)
but not both.
The former uses co-variant return types, and it is quite
possible there is a bug in the Kawa compiler in that area.
So if that doesn't work, use the latter.
I don't know how Jooby introspection works.
Looking at Java source files feels like a weird thing to do.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2021-09-07 20:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 19:03 Phil Eaton
2021-08-30 16:40 ` Per Bothner
2021-08-30 23:09 ` Phil Eaton
2021-08-30 23:18 ` Phil Eaton
2021-09-07 10:59 ` spellcard199
2021-09-07 13:02 ` Phil Eaton
2021-09-07 17:58 ` spellcard199
2021-09-07 19:35 ` Phil Eaton
2021-09-08 14:14 ` spellcard199
2021-09-08 14:20 ` spellcard199
2021-09-07 19:31 ` Per Bothner
2021-09-07 19:45 ` Phil Eaton
2021-09-07 20:13 ` Per Bothner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ee223b16-fb46-995e-d092-6e7026672a7b@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.org \
--cc=phil@eatonphil.com \
--cc=spellcard199@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).