| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
This is a somewhat obnoxious change in its scope and requirements,
but it makes it easier to understand what the real public and
private parts of our APIs are.
|
| |
|
|
| |
This breaks surprisingly little.
|
| |
|
|
| |
In C tor, this saved a whole lot of RAM.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Previously, every call to peek() or next() would call self.pred().
But this would run us into trouble if we were using a closure that
had mutable state, since it would stop us from checking for things
like "the third occurrence of the foo token".
Now we store the value of self.pred(self.peek()).
|
| |
|
|
|
|
| |
We need to have the Peekable be long-lived, so we can't consume it.
We _could_ create a second Peekable, which is apparently what we
have been doing, but that breaks down when we try to do it again.
|
| |
|
|
|
| |
I want the "peekable iterator" type to be passed around a lot, and
it needs to have some way to get at the string that's used with it.
|
| | |
|
| |
|
|
|
| |
Now that we are okay with using slice offset pointer math, we can
remove the 'off' field from Item entirely.
|
| | |
|
|
|
Arti is a rust tor implementation. It's project I've been working
on for a few months now, in weekends and in spare time. It doesn't
speak the tor protocol yet, and it doesn't connect to the network at
all.
It needs much more documentation and testing, but I'm just about
ready to show it to others. See the README.md for a description of
what is there and what isn't.
|
