traversing

Not only does that remove oceans of attack surface, but it also means you can read email without the emails themselves traversing the network.

Collection can happen any time and requires traversing large amounts of memory to see what is free and what isn't.

Running this for some weeks would allow them to build up a list of people traversing a certain route daily.

Recursion is evidently the better form for traversing data structures based on recursively enumerable types.

One of my pet peeves is that developers rarely understand the costs of traversing boundaries well enough to even think about them.

Generation GC beats malloc/free in the case of 'all objects allocated on the heap' when: sizeof(survivors) + cost of traversing survivors pointer fields + rewriting the remembered set < traversing malloc/free trees for allocation/freeing.

The big tech companies already support legal intercept for content traversing their networks.

There is a cost to traversing references; card marking and generational collectors just reduce the amount of references you need to visit, but it doesn't mean reference chasing isn't requiring extra instructions.

For typical webapps it wouldn't help because of the difficulty traversing firewalls.

It made traversing the mirror city a lot easier.

It’s this traversing of abstraction and concrete implementation that I believe takes someone past the early stage and into the junior programmer world.

That's not the type of interface you'd want to build algorithms on which are constantly and deeply traversing data object links, if any type of performance is required.

Traversing the heap and actually replacing references could actually be a good trade-off.