Linus Groh

Relevant sections from INTREPRETING.md that allow to infer this conclusion but could be more explicit: > All tests are declared as text files located within this project's test directory. >...

If anyone wants to make a PR that would be most welcome :) There already is dynamic detection of which base directory to use, this should be simple to add.

> We should always use ipcMain and ipcRender for communication between these to layers. Just being into electron for some days, what would be the alternative? At least the docs...

Anyone except me still working on anything? :thinking:

@n3storm There are two open PRs with no response from the maintainer whatsoever, though.

See https://github.com/bterlson/eshost/pull/116 :) Currently blocked on lack of PR review AFAICT.

This means the [test](https://github.com/tc39/test262/blob/main/test/language/expressions/assignment/S11.13.1_A7_T3.js) linked in the referenced issue will be invalidated and needs to be updated or removed, correct?

Likely relevant: https://github.com/rust-lang/rust/blob/2259028a70d6e1a44ad2cfd81955b577a43e8ef6/library/std/src/sys/pal/unix/stack_overflow.rs#L344-L349

The implementation for musl `pthread_getattr_np` is here: https://github.com/kraj/musl/blob/2c124e13bd7941fe0b885eecdc5de6f09aacf06a/src/thread/pthread_getattr_np.c#L15-L21 (highlighted part relevant for the main thread) glibc is vastly more complex and involves reading `/proc/self/maps`: https://github.com/bminor/glibc/blob/d49cd6a1913da9744b9a0ffbefb3f7958322382e/nptl/pthread_getattr_np.c#L76-L165

I also looked at Python which is known to be very portable and handles stack overflow - they [elaborately hardcode a recursion limit](https://github.com/faster-cpython/cpython/blob/258408239a4fe8a14919d81b73a16e2cfa374050/Include/cpython/pystate.h#L193-L215) :facepalm: I'm unsure if Rust deals with...