Compare commits
No commits in common. "7292c6a39abe3b19004898657ec401b802477caa" and "7410c1ff20d9bc799c017403dfdec34998a3614f" have entirely different histories.
7292c6a39a
...
7410c1ff20
5 changed files with 0 additions and 25 deletions
|
|
@ -1,7 +0,0 @@
|
|||
i have some work which might take care of this which is happening here:
|
||||
|
||||
entomologist:cffd805252f9a2b4373abf7852d9e750
|
||||
|
||||
this creates a new type Entry<T>, which has the basic author / creation-time / id as files, and then stores T in the filesystem however it likes to be stored.
|
||||
|
||||
it's still a ways off, but maybe it's worth waiting for so we don't have duplicate work? and for now we can just live with the git log penalty.
|
||||
|
|
@ -1 +0,0 @@
|
|||
sigil-03
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
got the initial framework laid out tonight - some of the naming i'm still not happy with, so it'll take some staring at that to figure out what feels right.
|
||||
|
||||
i'm not entirely sure the direction of... type responsibility..? that this is implementing is correct either, but we'll see.
|
||||
|
||||
right now i have a two test cases, one which is passing, and the other which isn't passing yet, because i still have `todo!()`s for the vec implementation (needs to make a dir)
|
||||
|
||||
dir naming is another thing i'm not totally happy about yet as well.
|
||||
|
||||
|
||||
but it's a start!
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
make generic Entry<T> type which can get put in FS
|
||||
|
||||
make a new type, Entry<T: Enterable> which allows things to get put into / taken out of the filesystem
|
||||
|
||||
|
||||
branch: `03/entries`
|
||||
|
|
@ -1 +0,0 @@
|
|||
inprogress
|
||||
Loading…
Add table
Add a link
Reference in a new issue