00:03:55 -!- jaboja has quit (Ping timeout: 240 seconds).
00:16:08 -!- tromp_ has joined.
00:18:13 -!- jaboja has joined.
00:30:50 -!- tromp_ has quit (Remote host closed the connection).
00:32:38 -!- adu has joined.
01:02:28 -!- tromp_ has joined.
01:12:48 <HackEgo> [wiki] [[MATL]] http://esolangs.org/w/index.php?diff=45878&oldid=45875 * Luis Mendo * (+3) /* Compiler */
01:14:11 -!- tromp_ has quit (Remote host closed the connection).
01:15:23 -!- hppavilion1 has changed nick to hppavilion[1].
01:16:19 * tswett smashes his fist on the game board, sending pieces flying.
01:16:42 <tswett> I've been thinking about a topological version control system.
01:17:44 <tswett> In a version control system such as git, you keep track of a bunch of revisions, all of which are states that your source tree can be in.
01:18:22 <tswett> You don't keep track of *how* things changed from one revision to the next; you just store a state, and then the following state, and call it good.
01:18:58 <tswett> With my version control system, you can't just specify a starting state and an ending state; you also have to specify a topological path between them.
01:19:56 <tswett> A point in the path could be a completely specified source tree, or it could be a *partially* specified source tree.
01:20:52 <tswett> So, perhaps "ACD" and "ACE" are possible source trees. "AC(unspecified)" is, obviously, not completely specified.
01:21:30 <tswett> Let's just write that as "AC*" for convenience.
01:22:20 <APic> I have a Déjà-Vu
01:22:31 <tswett> The rule for the topology is the following. A set is open whenever, for every partially specified source-tree it contains, it also contains all "more completely specified" versions of it.
01:22:36 * APic finished Munching, then i seriously need to go to Bed
01:22:53 <tswett> lifthrasiir: but "AC" and "ACEFSDALKJ" are valid fillings of it.
01:22:56 <lifthrasiir> (hmm, was a bit sleepy and had a bad joke, sorry)
01:25:45 <tswett> Now, a "path", in practice, is going to be a sequence of states, where two consecutive states differ by one of them being a more specified version of the other.
01:25:51 -!- tromp_ has joined.
01:26:15 <tswett> lifthrasiir: it does? I've used Mercurial, and I don't remember it having anything like partially specified states.
01:26:42 <lifthrasiir> ah, that would be a difference (and actually I don't yet get the idea of partially specified tree)
01:27:06 <tswett> Let's forget trees; let's say that this version control system only deals with single strings.
01:27:58 <tswett> "ACD" and "ACE" are valid strings. "AC*" isn't a valid string; it's a "partially specifed state", referring to any of various strings.
01:27:59 -!- ^v has joined.
01:28:35 <lifthrasiir> tswett: still "AC" *is* a valid string, right?
01:29:45 <tswett> We have individual points or states.
01:30:12 <tswett> We also have paths, which are composed of atomic changes that can be made. These are like edges in a graph.
01:30:17 <tswett> And we can take that further!
01:31:34 <tswett> There are also things corresponding to faces, or 2-cells, and then there are also 3-cells, and...
01:31:42 <tswett> Well, let me summarize.
01:32:00 <tswett> A "0-cell" is just a state. AC* or BCE or whatever.
01:32:14 <tswett> A "1-cell", or path, explains "how to get from one state to another".
01:32:30 <tswett> Then there are also "2-cells", which explain "how to get from one path to another".
01:32:53 <tswett> You might imagine that, for some reason, a single revision has two different histories behind it.
01:33:57 <tswett> There's an initial revision, and a final revision, and two distinct ways of getting from the initial revision to the final revision.
01:35:28 <tswett> You might want to have some sort of explanation of how the two histories are equivalent.
01:37:29 <tswett> Now, I've gotta go to bed, so I can't explain further.
01:38:44 -!- Phantom__Hoover has joined.
01:42:00 -!- Phantom_Hoover has quit (Ping timeout: 256 seconds).
02:06:02 -!- tromp_ has quit (Remote host closed the connection).
02:14:06 -!- gde33|2 has joined.
02:16:26 -!- gde33 has quit (Ping timeout: 276 seconds).
02:34:35 -!- mihow has quit (Quit: mihow).
02:38:10 -!- andrew_ has joined.
02:49:28 -!- adu has quit (Read error: Connection reset by peer).
03:00:05 <oerjan> shachaf: ooh (list), our hero returns just in time to save the day and be obliterated for it
03:04:58 -!- Phantom__Hoover has quit (Ping timeout: 272 seconds).
03:06:40 -!- tromp_ has joined.
03:10:52 -!- tromp_ has quit (Ping timeout: 250 seconds).
03:27:42 <oerjan> <hppavilion[1]> HTF do you spell that word!? <-- exorcise hth
03:30:53 <oerjan> <hppavilion[1]> And see what happened <-- obviously dwarfs developed mecha in the 1500s, then conquered the other races hth
03:41:11 <FreeFull> It's like exercise but the second e is an o
04:05:47 -!- tromp_ has joined.
04:33:38 -!- mauris has quit (Quit: Leaving).
04:37:33 -!- TellsTogo has joined.
04:44:02 -!- MDude has quit (Ping timeout: 250 seconds).
04:58:39 -!- jaboja64 has joined.
05:02:15 -!- jaboja has quit (Ping timeout: 250 seconds).
05:06:26 -!- jaboja64 has quit (Ping timeout: 240 seconds).