BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//juliacon-2026//talk//LYBBPW
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-juliacon-2026-LYBBPW@pretalx.com
DTSTART;TZID=CET:20260812T154500
DTEND;TZID=CET:20260812T160000
DESCRIPTION:Type-piracy is often said to be "defining foreign behavior over
  foreign types".\n\nSounds intuitive\, but in practice things get complica
 ted quickly: A basic type like `ForeignType{Float64}` may be "obviously fo
 reign"\, but how do we extend that notion to Julia's full type language in
 cluding `Union` and `where`? Are all forms of type-piracy equally bad\, or
  is "type-privateering" a thing? Most importantly\, how does this affect y
 our code in practice?\n\nThis talk will attempt to construct a mathematica
 lly precise definition for the "essence" of type-piracy. We'll discuss how
  determining type-piracy might be automated and what it would mean to make
  this a "first-class" restriction in Julia. Do we lose expressivity\, gain
  performance? What designs would this affect in practice?\n\nAlong the way
 \, we'll examine cases of "type-piracy in the wild" in the community (and 
 even in Julia's own standard libraries!). These controversial case studies
  will serve as a litmus test to see if we can conquer the type seas\, or i
 f the age of the type-privateer continues.
DTSTAMP:20260502T110621Z
LOCATION:Room 1
SUMMARY:Bringing Order to the Seas: Defining Type-piracy in Julia - Cody Ta
 pscott
URL:https://pretalx.com/juliacon-2026/talk/LYBBPW/
END:VEVENT
END:VCALENDAR