From: Per Bothner <per@bothner.com>
To: Vasantha Ganesh <vasanthaganesh.k@gmail.com>, kawa@sourceware.org
Subject: Re: Proposal draft
Date: Mon, 03 Apr 2017 14:39:00 -0000 [thread overview]
Message-ID: <6bf1f672-582d-3a64-46c5-f38805df5ee4@bothner.com> (raw)
In-Reply-To: <CAL0TjKoAyg6Oa_pmm1PQCQ6GEozxC5f7i_GckWmT5p_1pKxUJA@mail.gmail.com>
On 04/03/2017 07:15 AM, Vasantha Ganesh wrote:
> Hello all,
>
> I've managed to write a proposal for the idea "Optimized function
> types and values using MethodHandles"
>
> Here is the first draft:
>
> https://docs.google.com/document/d/1khL_gUy1-G7NDdJHTGNom3r2UXs8YTYEJNc-Ch0yuyo/edit?usp=sharing
awesome-sauce-function :: int -> int -> bool
(define (awesome-sauce-function parm1 param2)
(> (+ param1 param2) 0))
First, you have to realize that syntax would not "fit in" very well with
a language that uses Lisp syntax (even one with as many extensions as Kawa).
I think it would be quite difficult to parse.
Second, it's not needed. Kawa already has a perfectly ok syntax for type signatures:
(define (awesome-sauce-function parm1::int param2::int)::boolean
(> (+ param1 param2) 0))
This project is not about typing and checking of specific functions, which Kawa
does quite well. It's about typing of function *expressions* and variables - for example
a function-valued parameter in a higher-order function.
I.e. to express things like: "I don't know the value of this variable, but I know it some
(unknown) 2-argument function that takes two ints and returns a boolean."
Sorry, I don't think this proposal is salvageable in the amount of time we have.
Maybe next year?
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2017-04-03 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 14:15 Vasantha Ganesh
2017-04-03 14:39 ` 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=6bf1f672-582d-3a64-46c5-f38805df5ee4@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.org \
--cc=vasanthaganesh.k@gmail.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).