From bf62cf2866ade95c8569f344051295d4b36dd00d Mon Sep 17 00:00:00 2001 From: bpcreech Date: Tue, 9 Apr 2024 21:10:34 +0000 Subject: [PATCH] Apply formatting changes --- content/post/mini-racer-v0.11.1.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/post/mini-racer-v0.11.1.md b/content/post/mini-racer-v0.11.1.md index 14556be..532248e 100644 --- a/content/post/mini-racer-v0.11.1.md +++ b/content/post/mini-racer-v0.11.1.md @@ -673,8 +673,9 @@ what happens now is: I think the design strategy is generalizable to most Python/C++ integrations, and potentially likewise Java/C++ and C#/C++ integrations. (_TL;DR: use integer identifiers instead of passing pointers, track object lifecycle in maps on the -C++ side, validate all incoming identifiers from Python, and refactor so that out-of-order finalization doesn't hurt -anything_). I wonder if it's written down anywhere. +C++ side, validate all incoming identifiers from Python, and refactor so that +out-of-order finalization doesn't hurt anything_). I wonder if it's written down +anywhere. ## Contribute!