Post #1809100

In PL we spend a lot of time thinking about how to ensure that type systems or program analysis tools are sound: that they only make valid predictions about code's behavior. (Or at least, are sound with a few explicitly identified exceptions like reflection.) But sometimes we get it wrong. Or sometimes we do get it right, but only after trying something more obvious that seems like it should be right, but turns out to be wrong. Or we get it right in theory, but there's an extra wrinkle in the implementation that wasn't obvious but affects soundness. The UNSOUND workshop colocated with ECOOP in Brussels this summer is looking for talk proposals around these and other related topics. If you think you have something interesting to talk about, please submit a talk proposal! The workshop is pretty low-key, I had a great time attending in 2024 (it's biannual). https://2026.ecoop.org/home/unsound-2026