layout | title | permalink | schedule | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
page |
Schedule |
/schedule/ |
|
We expect to be following Shonan's standard template for a 5-day meeting. In a nutshell:
<style> .schedule td, .schedule th { vertical-align: top; } .schedule a { position: relative; display: inline-block; } .hover { font-size: 10pt; } .schedule a .hover { visibility: hidden; opacity: 0; transition: opacity 0.3s ease-in-out; min-width: 300px; background-color: black; color: #fff; padding: 1em; border-radius: 6px; position: absolute; z-index: 1; } .schedule a:hover .hover { visibility: visible; opacity: 1; } </style>{% assign time_slots = "07:30-09:00,09:00-10:30,10:30-11:00,11:00-12:00,12:00-13:30,13:30-15:30,15:30-16:00,16:00-18:00,18:00-19:30,19:30-21:00,21:00-" | split: "," %}
{% for day in page.schedule %} {% endfor %} {% for time_slot in time_slots %} {% for day in page.schedule %} {% endfor %} {% endfor %}{{ day[0] | replace: " ", " " }} | |
---|---|
{{ time_slot }} |
{% for event in day[1] %}
{% if event.slot == time_slot %}
{% if event.short_title %}
{{ event.short_title }}
{% if event.description %}
|
Details of the individual sessions are at the foot of this page.
Each technical session will have one person nominated as a discussant. The responsibility of this role is to end the session by responding to the presentations in that session. This might be to provide a personal comment on the presentation; it might be to explain some of the context; it might be to raise some questions, or even (constructively!) criticize the presentation or point at shortcomings.
The goal of the discussant's time is to spark discussion. This can be discussion between them and the presenter, but it's even better if they can manage to draw the audience into the discussion. The point is to help everyone think about and reflect upon the presentations that have just taken place. It also serves to enhance the workshop feel, with more people engaging in discussion and discussing the impact of the work being presented as well as potential unsolved problems.
Please contact us if you would like to volunteer as discussant for a particular session. We will volunteer people on Monday morning to fill the remaining discussant roles.
There are panel discussions at the end of Tuesday and Thursday. We have allocated an hour for each of these, but in a two-hour session at the end of the day. The idea here is that if the discussion has run its course after an hour, we have time to relax and chat before dinner; if the discussion is still going, yet you've have enough for the day, you can leave with honour after an hour; but we hopefully do not need to impose a hard stop and stifle a lively discussion.
We will organize these panels as fishbowl discussions. The panel will be initialized with four "fish", but five chairs; at any point, anyone else can join the fishbowl to speak, and one of the current fish must volunteer to leave. The point is to allow everyone to have a say. The initial fish are: Ningning, Sam, Taro, Philipp on Tuesday; Shin-ya, Eli, Yukiyoshi, Cameron on Thursday.
Participants suggested the following puzzles and problems that we might discuss, during breaks or after dinner. We can revisit these on Friday in case there are outcomes to report.
- Interesting applications that require both deep and shallow handlers
- Solution to the "Reflection without Remorse" problem without reifying computation as data (maybe relate to shallow handlers?)
- Handler-based reinforcement learning: On Reinforcement Learning, Effect Handlers, and the State Monad, Smart Choices and the Selection Monad
- Algebraic theories for practical handlers, eg for concurrency
- Language Server Protocol
- Interactive tutorial for effect handlers
- A new Benchmark Repo Tsar
- Using only continuations (that is callcc, but no assignments etc), find a term
e
and a context C such that:C [ (\x -> (x,x)) e ]
andC [ (\x y -> (x,y)) e e ]
evaluate to different values (Amr).
{% for day in page.schedule %}
{% for event in day[1] %} {% if event.short_title %} {% if event.description %}-
{% for item in event.description %}
- {{ item }} {% endfor %}