Pattern Matching

[John Rose]

On Mar 28, 2017, at 1:04 AM, Andrey Breslav <andrey.breslav at jetbrains.com> wrote:
> 
> For completeness, since Remi aimed at listing all alternatives, I think we should not forget Object algebras: https://www.cs.utexas.edu/~wcook/Drafts/2012/ecoop2012.pdf <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.cs.utexas.edu_-7Ewcook_Drafts_2012_ecoop2012.pdf&d=DwMFaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=lHQQP_21o1x25cljBzJfny3WhZfis9i1l__EQId-YS8&m=S66HlLkIAVyLjybndnX757FqKMVc09aizAFtTfO3bYk&s=VFuju0jCypu8uUv-_3IsX8DrsJuMu-TdIAWGnpE5dMU&e=>
> 
> My experience has been that this pattern is good for observing data structures (transforming, pretty-printing, etc), but it's usually hard to implement, say, equals() through it

Thanks for the reference.  Cook's work on batches is probably relevant.
There is something deep going on here, and that paper shines some light on it.
I hope we can connect Java deeply to the sorts of patterns they talk about.

Since matching is not (yet, officially) on the table for Amber, it would be
premature to use this venue to say much more.  One teaser: I hope
to get some time to write about what I think of as "metamorphic programming",
or coordinated hooks for the "tear down" and "build up" of data.

— John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/amber-spec-experts/attachments/20170329/f327e8be/attachment.html>