| 11 Dec 2025 |
 hexa | markdown 😄 | 22:38:51 |
 piegames | Draw the rest of the owl I guess | 22:38:51 |
| hexa | ${foo} = "bar"
but you can do
foo.${bar} = "baz"
| 22:39:25 |
 KFears (they/them) | I don't have a structured view of it, but in general, something at the intersection of modules and the type system strikes me as odd, and makes me feel like modules are a very "DIY" kind of thing that you have to reimplement from scratch, and I guess I'd be happy if the language could help with that, though I'm not sure where to take it | 22:39:29 |
| hexa | * can't do
${foo} = "bar"
but you can do
foo.${bar} = "baz"
| 22:39:34 |
 emily | overlays can be quite easily typed with row types. | 22:39:56 |
| KFears (they/them) | Yeah, that's also weird... I'm not sure about it, like, it's convenient, but it feels weird, like I'd maybe expect a builtin that allows creating those kinds of arbitrarily-named attributes instead of it being a syntax thing | 22:41:57 |
| emily | e.g.
Overlay : Row -> Row -> Row -> Type
Overlay Final Prev Extra = {...Final} -> {...Prev} -> {...Extra}
data Overlays : Row -> Row -> Type where
nil : forall Final. Overlays Final {}
cons : forall Final Prev Extra. Overlay Final Prev Extra -> Overlays Final Prev -> Overlays Final (Prev // Extra)
addsFoo : forall Final Prev. Overlay Final Prev {foo : …}
addsFooUsingBar : forall FinalR Prev. Overlay (FinalR // {bar : …}) Prev {foo : …}
changesFoo : forall Final PrevR. Overlay Final (PrevR // {foo : …}) {foo : …}
changesFooUsingBar : forall FinalR PrevR. Overlay (FinalR // {bar : …}) (PrevR // {foo : …}) {foo : …}
(function to evaluate these left as an exercise)
| 22:48:44 |
| emily | I'd say it's not really that much different to typing TypeScript objects tbh | 22:49:49 |
 raitobezarius | ~~Now do IFDs~~ | 23:20:26 |
 Charles | Box<dyn Any> | 23:25:25 |
