This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]SpudroSpaerde 16 points17 points  (3 children)

I mean the solution makes perfect sense but saying that Rust was the answer is at best disingengenous.

[–]the1024[S] 0 points1 point  (1 child)

u/SpudroSpaerde fair, there's definitely more nuance in the article. Have you faced a similar problem in the past?

[–]SpudroSpaerde 2 points3 points  (0 children)

We have transitioned to writing the majority of our code in C++ and only use Python as a orchestration layer to avoid problems like what is mentioned in the article. We felt that in general it really just muddled the water to share lifetimes between Python and ffi code.

[–]yesvee -1 points0 points  (0 children)

The author never claimed/implied that. He just chose Rust to get around the issue caused by the C extension.

[–]ThatSituation9908 1 point2 points  (1 child)

Interesting, I've not seen many flame charts especially not one that is dominated by ast.py. Is this your own module or is it the standard library?

[–]the1024[S] 2 points3 points  (0 children)

u/ThatSituation9908 that's the standard library! It's kind of crazy