bigs

@Stebalien i misspoke earlier when i said serialization was the issue. it's only deserialization. there's a somewhat prevalent pattern, for example in the datastores, of having something like `NewBadgerDatastore(...) *BadgerDatastore`...

ah, you know, that's a fair point. i think it's still probably worth it, because it would only be *adding* functionality, not removing or hindering anything. that said, it would...

i think this is a definite case for indexing, as you suggest. a note: we can also open multiple badger data stores instead of namespacing keys if it suits. it’s...

FWIW, i've recently done some work with the go-onion-transport. it is admittedly in pretty bad shape, but i've got plans to rebuild it atop a newer tor library, [bine](https://github.com/cretz/bine). bine...

ah, good thoughts. i think an external lib would be fine :) i've tinkered with plenty of haskell impls in the past, so i'll take a peek at those, reflect...

@paluh lovely! going to dig into these this afternoon. not finding a ton of resources on it and i'm fairly new to PS (tho quite experienced w/ haskell & ML)—what...

an update—things picked up quite a bit with the client so i'm only now getting to frontend work. this is still something i'm interesting in pursuing! i think it will...

bumping this! i've since embarked on a rather extensive project and found that `Data.Codec` is a perfect fit for this. my approach will probably be extending `purescript-routing` to accept codecs....

just chiming in with a thought, but skip lists could be a wonderful aid in parallelizing mark passes!

basically using the skip lists as a means of dividing up the work. each thread gets an id (i) from [0..num threads) and finds its "batch of work" by traversing...