BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//juliacon-2025//talk//S9HMM9
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-juliacon-2025-S9HMM9@pretalx.com
DTSTART;TZID=EST:20250725T103000
DTEND;TZID=EST:20250725T110000
DESCRIPTION:When you write a float range like 0.1:0.2:0.7 it seems obvious 
 that you want the elements to be 1/10\, 3/10\, 5/10\, 7/10. But the floati
 ng-point numbers 0.1\, 0.2 and 0.7 are not exactly 1/10\, 2/10 and 7/10—
 they are approximations of the form m/2^p. Guessing what any given float r
 ange was intended to mean turns out to be shockingly hard. Julia currently
  uses a heuristic that mostly works but still has some rather unfortunate 
 failures. This talk explores how to solve this problem once and for all.
DTSTAMP:20260610T190459Z
LOCATION:Lawrence Room 104 - Function Room
SUMMARY:Why are float ranges so hard\, and can we do better? - Stefan Karpi
 nski
URL:https://pretalx.com/juliacon-2025/talk/S9HMM9/
END:VEVENT
END:VCALENDAR