14:08:55lokeThe separation between types and variables is still a bit fuzzy
14:22:10lokebeach: This is the current brain dump: https://drive.google.com/file/d/1aaVZmegLT42ur17j7Vbtdh7auco7pmYN/view?usp=sharing
14:22:37lokeHere's the repository, but there isn't much in it: https://github.com/lokedhs/lisp-pref
14:25:07phoeloke: your work partially overlaps with my PROTEST way of declaring configuration categories and configuration options.
14:26:49phoeDEFINE-TYPE is not the best name because it directly clashes with CL:DEFTYPE. Maybe something more verbose like DEFINE-CONFIGURATION-TYPE?
14:27:32phoe:STRUCTURE :STRING is unclear to me. I don't yet get what it does, and also you missed a closing paren. (:
14:28:56phoeUsing hash-tables is a better idea. Any list of non-null lists is a valid alist, and therefore you might avoid type confusion by using hashtables.
14:31:26phoeSo it is obvious that you don't want just a mere tree of valid lists, and instead you want an actual map from keys to values.
14:31:39phoeThat's the stuff I've thought of so far.
15:19:35shka_soooo, there is this successor to prove called rove
15:21:38comborico1611Which word would you use to describe the difference between a Lisp REPL to that of all the other programming language REPLs? I was thinking "memory".
15:30:18comborico1611shka_: Hmm. There may be more than one difference then. I was thinking on the ability to load a function onto the REPL and then call it again.
16:18:09phoeI've only started to rewrite my old code using my new version of PROTEST and I'm already uncovering things that I should have done better back in the day
16:18:32phoesuch as discovering that I have duplicated DEFGENERICs and I should instead create a new mixin
17:22:50phoeIn PROTEST, a category is not particularly interesting - the category only really exists to be a reference for the programmer, and for having a docstring.
17:22:59loke(besides, protest is definitely somehting I need. Potato has already changed test frameworks once)
17:23:11phoeAnd a configuration entry is essentially what you describe - a value, accessed by a list of keywords.
17:23:52lokeI have to go to sleep now. I'll check it later.
17:24:47phoeloke: PROTEST isn't an abstraction over different testing libraries. It still forces you to write tests in a given test library, but it provides mechanisms for generating test cases that are textual descriptions of tests, and therefore independent of given test implementations.
17:26:09phoeloke: a library abstracting over multiple different testing framework would be a testing framework itself. And we already have enough of these.