mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.2 2025-03-04T17:33:25Z 2025-03-04T17:33:25Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-03-04T15:39:48Z urn:sha1:11049b07c419fc7544c382a98ea8366d6b468daf Let's use Tokio terminology here. 2025-03-04T17:30:43Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-26T16:03:43Z urn:sha1:878c32bc1e9027fa3cf405c87f5323b94969b0fb Forbid re-entering the executor using ToplevelBlockOn::block_on. This was always forbidden in the case of MockExecutor, but that meant that tests using MockExecutor would malfunction if the code under test needed to re-enter the executor from sync code (since the code under test would have to use block_on, which wrong). See #1835. Provide a function which *can* do this, reenter_block_on. The MockExecutor needs to know the difference, and other runtimes may too. They are conceptually quite different operations. Introduce ToplevelRuntime as a convenience alias. 2025-03-04T17:30:43Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-25T14:10:35Z urn:sha1:20eabfcc81a2d0df61ce297b28c7412c3ceab7fd * Document the new plan for blocking interaction in the trait-level docs for the Blocking trait (used to be SpawnBlocking). Add cross-references (in some cases to not-yet-existing pieces). * Rename: spawn_blocking to spawn_thread. We're going to distinguish thread-creation (relatively expensive) from brief entry to sync code (relatively cheap, but more restricted). * Rename the SpawnBlocking trait to Blocking, and its ThreadHandle to ThreadHandle. This trait is going to gain more functionality. * Add the missing mention of `Blocking` to the docs for `Runtime`. 2025-03-04T17:30:43Z Ian Jackson ijackson@chiark.greenend.org.uk 2025-02-13T17:39:39Z urn:sha1:849558047071897b9bbdbdd28d06d15b52b3af10 We're going to distinguish top-level runtime entry, from *re*-entry to an existing executor. It is most convenient to rename this trait first. Documentation of the distinction will come later. (We're going to retain the function name `block_on`, but we want the trait to be more obviously a top-level only thing, though, so we give it a name that will hopefully avoid it peroulating throughout the codebase..) 2025-01-15T13:49:17Z Gabriela Moldovan gabi@torproject.org 2025-01-08T19:08:57Z urn:sha1:f04709c16d0ebf039779c404cf0c907f13965852 This is unfortunately necessary, because after the channel handshake, we need to give the channel reactor a `StreamOps` handle to the underlying stream. 2025-01-07T18:27:14Z Wesley Aptekar-Cassels me@wesleyac.com 2024-12-19T19:30:29Z urn:sha1:665d3145a0db86bd1fbd7549b64e21a160c45ff1 Due to the limitations on RPIT, it's better to use a GAT for now. 2025-01-07T18:26:28Z Wesley Aptekar-Cassels me@wesleyac.com 2024-12-18T20:57:30Z urn:sha1:5f91a2b5fa6f343a51cc325ee7a9519f7523d14c This adds a new SpawnBlocking trait, which exposes the spawn_blocking function that tokio, async-std, and other runtimes have. 2024-10-29T17:36:16Z Nick Mathewson nickm@torproject.org 2024-10-29T17:36:16Z urn:sha1:7ddd8bacdfbd91356805a37e15c023e3b525b6e8 2024-09-24T13:10:11Z Nick Mathewson nickm@torproject.org 2024-09-22T19:17:14Z urn:sha1:7a56ae00ffb6e45783b0eb837098ea894ade5861 2024-09-24T13:10:11Z Nick Mathewson nickm@torproject.org 2024-09-19T11:55:22Z urn:sha1:8c2d84000e4d5ba74e7b6b4e9dac3fc700f618b5 (And similarly rename TcpListener to NetStreamListener, along with their TcpStream/TcpListener associated types.) These types are about to become generic over addresses, and therefore shouldn't be named after TCP. Renaming was done mostly with Rust Analyzer, except for some macros that needed to be hand-edited. (I'll revise the comments in the next commit; this one is all about renaming.)