Conversation

yeah, if field names are actually named entities, that problem goes away, altho I suppose it raises the question of where those are defined… who namespaces the namespaces themselves? quis namespa… you know what, never mind the mock-latin
1
1
Yeah! It gets a bit weird! Clojure lets you have ‘namespaced symbols’ but that requires a top level namespace thingy. Where as I would love to be able to get rid of the top level ‘command’ language (like in Dhall and Nix)
1
2
Similar problem in my formalism: lambdas are scope + readerish effect. But definitions of ops are functions. Where do you tie the knot? (Currently thinking about jumps instead of functions.)
1
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
like, what are records, telescopes, and functions actually doing? 😳 - somehow a record field is 'stronger' than a function parameter - ie. a function can be constructed even if there is no way of providing a parameter, where as a record kind of *insists* that a field is present.
2
1
ok so! this is sort of an evaluation order thing. in a lazy lang you can construct a record w/o providing each field by using e.g. fix id as the value of the field—something divergent—and just not touching it
1
(obvs if the lang/field is strict, that doesn’t work.) so the records you’re thinking of are strict ones. in a polarized lang, that’s probably the same as positive records.
2