From c8f58052b20ce613237dc05d73f5c15f9760fb55 Mon Sep 17 00:00:00 2001 From: Johan Milanov Date: Sun, 10 Dec 2023 17:36:30 +0100 Subject: [PATCH] Fix typo in 2023-12-10-nsfw.dj --- content/posts/2023-12-10-nsfw.dj | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/2023-12-10-nsfw.dj b/content/posts/2023-12-10-nsfw.dj index e0fe82bd..843bb666 100644 --- a/content/posts/2023-12-10-nsfw.dj +++ b/content/posts/2023-12-10-nsfw.dj @@ -250,7 +250,7 @@ Another breakage example is various OS APIs that just mandate that things happen execution thread, like `pthread_mutex_unlock`. Though I think that the turtle those APIs stand on are thread locals again? -Can we fix it? As an absolute starwman proposal, let's redefine `Send` & `Sync` in terms of abstract +Can we fix it? As an absolute strawman proposal, let's redefine `Send` & `Sync` in terms of abstract "execution contexts", add `OsThreadSend` and `OsThreadSync`, and change API which involve thread locals to use the `OsThread` variants. It seems that everything else works?