From: Anil Madhavapeddy <anil@recoil.org>
To: Kakadu <kakadu.hafanana@gmail.com>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] About recently dead compiler-hacking wiki
Date: Fri, 30 Sep 2016 14:07:32 +0100 [thread overview]
Message-ID: <F3A8B3A3-5325-4EAA-A0C7-770603AF6BF4@recoil.org> (raw)
In-Reply-To: <CAGmVoG03SyOn1x-c9DXw2FrrVbE=RsaQLVb=kv46FUkyALfhvQ@mail.gmail.com>
On 30 Sep 2016, at 13:58, Kakadu <kakadu.hafanana@gmail.com> wrote:
>
> Hey, folks
>
> Compiler hacking is fun. Hacking compiler with a feature that can be
> potentially appreciated is a double fun. But ocamllabs wiki is dead.
> Do we have a list of crazy ideas for compiler on mantis or somewhere
> else to work ourselves or give to undergraduates as a pet project?
Umm, the above rumours of the death of the OCaml Labs wiki may be slightly premature.
https://github.com/ocamllabs/compiler-hacking/wiki/Things-to-work-on
...indicates that the project list isn't curated actively and that it's not authoritative to avoid misleading students, but the list is still a good source of interesting projects. Note that it's open for editing by anyone, so you are more welcome to help out by editing and refreshing any projects in there.
Cambridge Compiler hacking sessions took a hiatus for the summer, but will return soon for those in the region:
https://ocamllabs.github.io/compiler-hacking/
It would be great to see similar events in Paris or elsewhere if anyone is interested in organising them!
regards,
Anil
next prev parent reply other threads:[~2016-09-30 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 12:58 Kakadu
2016-09-30 13:07 ` Anil Madhavapeddy [this message]
2016-09-30 13:07 ` John Whitington
2016-09-30 13:33 ` Kakadu
2016-09-30 13:48 ` Gabriel Scherer
2016-10-01 0:07 ` Junsong Li
2016-10-01 5:22 ` Kakadu
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=F3A8B3A3-5325-4EAA-A0C7-770603AF6BF4@recoil.org \
--to=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=kakadu.hafanana@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 NNTP newsgroup(s).