braxxox

Joined 9 years ago

Karma
712
Submissions
74
Member since
Jun 11
[ my public key: https://keybase.io/brannondorsey; my proof: https://keybase.io/brannondorsey/sigs/-0yvnJKsOmsbR6E3WTdXr9L8u9q-YS2EmadgBvAXONE ]
View on Hacker News

Recent submissions

Comment · 10 days ago
Red October
Comment · 3 months ago
I've shipped a tour so you can try it out before signing up!
Comment · 3 months ago
Comment · 3 months ago
That's good feedback. Would it help if the sign up process happened after the welcome tour?
Comment · 1 year ago
Nadine would be proud.
Comment · 1 year ago
Comment · 1 year ago
I've proposed these changes to shy away from the claims of "Run unsafe code safely" in this crate.

Let me know what you think, or if you have any additional suggestions.

Comment · 1 year ago
I'm proposing that change here: https://github.com/brannondorsey/mem-isolate/pull/44

Let me know if you think this wording could be improved or I'm missing any details.

Comment · 1 year ago
Thanks for that suggestion.

I'm adding a few more limitations in this PR: https://github.com/brannondorsey/mem-isolate/pull/44

I know async-signal-safety is particularly important for, you know, signal handlers. But aside from those, and the multi-threading use case you describe, is there another use case where calling non async-signal-safe code from inside this module would lead to issues (that isn't covered in the new limitations)?

I can add another limitation is issues can transpire if the code you run in `callable()` isn't async-signal-safe, but I'd like to offer a few additional examples of gotchas or surprises to point out there.

Comment · 1 year ago
> have no hope of doing better

Yeah, this is really the main use case. Its a relatively simple solution when you can't do any better.

I think that's particularly helpful when you're invoking code you don't control, like calling into a some arbitrary C library.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton