Conversation

I do wish that telescopes and spines were less... listy... and more... graphy. So that more telescopes were equivalent, and more spines could be checked against them. That's why I find records and labelled args nice. Just unsure how to make it efficient in an implementation. 😰
1
3
I’m struggling to even make things work at the moment; inefficiency would be a nice problem to have, from that perspective ^_^;;
1
2
Yeah, well... I guess I have ideas how to make it work but that might not work in reality ; _ ; just hate how positional all the currying and pairing stuff is - as much as it's nice in some cases then stuff lines up properly
1
1
I had this weird (probably bad) idea to have records with 'abstract' fields that you could make concrete later - which would end up kind of being like functions? And you'd be able to have a 'default' field that your record would reduce to if all the fields were concrete.
2
1
Like I think generally it's considered good to have nice categorical models of your type systems, and alterations like this might break a bunch of that stuff? Or at least be a rather ad-hoc extension? All the category theory stuff is a bit mysterious to me though. 😰
1
yeah, I can usually make *some* headway on a sequent calculus judgement, but once the category theory’s out I might as well just drink
2
2
Show replies
Replying to and
All my instincts tell me that this particular variant is indeed a Bad Idea. You want your 'functions' to be continuous - which, in this case, means given by a uniform definition of the inputs. But in the same neighborhood of this idea, I'm sure there are some good designs.
2
2
Thanks! I will ponder more - definitely feel like I'm missing something. I was thinking of today was that: Σ (a : A). Π (b : B). C a b can be reordered to: Π (b : B). Σ (a : A). C a b but converse is not true, unless I'm horribly mistaken. 🤔
1
Show replies