BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//juliacon2023//speaker//EWDVK7
BEGIN:VTIMEZONE
TZID:EST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T070000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T080000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-juliacon2023-CNBSS3@pretalx.com
DTSTART;TZID=EST:20230728T161000
DTEND;TZID=EST:20230728T162000
DESCRIPTION:Type instabilities are not always bad! Using non-concrete types
 \, and avoiding method specialization and type inference can help with imp
 roving latency and\, in specific cases\, runtime performance. The latter i
 s observed in inherently dynamic contexts with no way to compile all possi
 ble method signatures upfront\, because code needs to be compiled at point
 s of dynamic dispatch by design. We present a concrete case we face in our
  production environment\, additional examples\, and related trade-offs.
DTSTAMP:20260715T134929Z
LOCATION:32-144
SUMMARY:When type instability matters - Théo Galy-Fajou\, Cédric Belmant
URL:https://pretalx.com/juliacon2023/talk/CNBSS3/
END:VEVENT
END:VCALENDAR