caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jon Harrop" <jon@ffconsultancy.com>
To: "'Yotam Barnoy'" <yotambarnoy@gmail.com>,
	"'Adrien Nader'" <adrien@notk.org>
Cc: "'Ocaml Mailing List'" <caml-list@inria.fr>
Subject: RE: [Caml-list] Google summer of code
Date: Wed, 15 Jan 2014 18:38:46 -0000	[thread overview]
Message-ID: <21c401cf1221$07484030$15d8c090$@ffconsultancy.com> (raw)
In-Reply-To: <CAN6ygOmfhphtKFzqfwZgtddLBMJcPWT9_G6kh8A+eSTYbnP1ew@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4428 bytes --]

Ø  I can say that the main part is coming up with a webpage full of ideas
for projects.

 

If anyone wants to pursue anything like HLVM, please do get in touch with
me.

 

I’ve been discussing student projects recently and a couple of ideas I’ve
had are:

 

1.       Merge core (stdlib) collections with the GC. For example, mutable
stacks and queues are currently represented as arrays filled with NULL
pointers whereas a collection-aware GC could skip the unreachable pointers
and the collection wouldn’t have to NULL out its elements. Collections could
also be shrunk by the GC.

2.       Allow objects to morph their representation as they go from one
generation to another. For example, long-lived immutable sets could morph
from a tree of heap-allocated blocks into a sorted array.

 

I also think it would be interesting to study how fast purely functional
data structures could be if their representation was optimized (within the
confines of a memory-safe VM) for the performance characteristics of a naïve
mark-sweep GC. For example, list cons in OCaml currently heap allocates a
new block based on the assumption that the GC can do this quickly (which
OCaml can) but the list implementation could pre-allocate a block of cons
cells in an array and use a CAS to claim the next one, amortising
allocations and greatly reducing the stress on the GC. I’ve implemented this
for lists in F# where it is about as fast as the generational GC. I don’t
know if the same can be done effectively for trees like Set and Map. The
motivation is avoiding the pathological performance for programs that
violate the generational hypothesis.

 

Cheers,

Jon.

 

From: caml-list-request@inria.fr [mailto:caml-list-request@inria.fr] On
Behalf Of Yotam Barnoy
Sent: 15 January 2014 15:24
To: Adrien Nader
Cc: Ocaml Mailing List
Subject: Re: [Caml-list] Google summer of code

 

I actually don't think it's very hard to apply (in general). The
requirements page is here
(http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc20
14/help_page?ModPagespeed=noscript#1._How_does_a_mentoring_organization).
It's certainly much easier than applying for a grant.

Having participated as a mentor in another organization, and having seen the
application process every year, I can say that the main part is coming up
with a webpage full of ideas for projects. I think that already exists
partially on the ocamllabs wiki. I'd really like to see that wiki be
centralized and available from the ocaml.org site. The key thing is to
figure out which projects are doable by people in one summer. The next step
is that people need to volunteer for mentorship. Even 2 people are enough
for a start, but 3-4 are better. Finally, one person takes on the process of
filling out the application and submitting it.

One of the things that concern google, as can be seen in the webpage, is
that there's enough effort from the mentors to 
a. weed out the poor candidates and 
b. be in touch with/demand enough from the candidates to make sure that
they're actually working and not just slacking off for the summer. In my old
organization, the participants had to post blog updates every week or so
about their progress.

Other than that, there's not much to it.

-Yotam

 

 

On Wed, Jan 15, 2014 at 4:04 AM, Adrien Nader <adrien@notk.org> wrote:

Hi,


On Tue, Jan 14, 2014, Yotam Barnoy wrote:
> Dear List
>
> Are there plans to apply for GSOC mentorship this year? Searching online
> yielded only a rejected application from 2011. Applications for mentor
> organizations are due February 14th.

Then, if nothing has been started yet, it's probably already too late.
GSoC is fairly constraining and time-consuming. Nowadays, projects which
manage to do it have actually gotten experienced at it and this makes it
more difficult for new participants: they don't only have to do things
well, they have to do things better than projects which have been doing
it for 10 years.

There's also a feeling that Google doesn't care about what happens in
OCaml-land (that's mostly speculation).

I believe it might be worth trying again. Many things have changed and
the projects that could be worked on now might appeal more to the GSoC
organizers. That would be for 2015 in my opinion though.

Regards,
Adrien Nader



 


[-- Attachment #2: Type: text/html, Size: 14980 bytes --]

  reply	other threads:[~2014-01-15 18:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 23:04 Yotam Barnoy
2014-01-15  9:04 ` Adrien Nader
2014-01-15 13:31   ` Nicolas Braud-Santoni
2014-01-15 15:23   ` Yotam Barnoy
2014-01-15 18:38     ` Jon Harrop [this message]
2014-02-26 11:17 ` Anil Madhavapeddy
2014-02-26 12:06   ` Marco Canini

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='21c401cf1221$07484030$15d8c090$@ffconsultancy.com' \
    --to=jon@ffconsultancy.com \
    --cc=adrien@notk.org \
    --cc=caml-list@inria.fr \
    --cc=yotambarnoy@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).