Hey all, to better separate the operational code of StarlingMonkey from the other things (scripts, cmake, Rust crates, etc) any objections to moving the C++ source code to src/
rather than having modules mixed into the top level directory?
It's a little thing but I think it would help repo organization a bunch.
That sounds like a good idea to me.
Is this urgent or can this wait for pending PRs to be merged? I have 3 PRs ready to go (File API, createObjectURL and FormData).
This can absolutely wait! I'll push up the PR I wrote as draft for now, and refactor as those others land!
Definitely don't want to hold up that progress :)
https://github.com/bytecodealliance/StarlingMonkey/pull/194
Would appreciate feedback on the cmake changes in the meantime, from anyone with spare cycles!
Welp, that was an incredibly painful exploration of cmake
. But now that refactor PR CI is finally :green:
Going to leave it in draft till some later date, either after the other stuff merges or next JS meeting
Ah forgot to bring this up in the meeting, but now that the other stuff has merged ahead of this, do we still want this PR to happen? If we're happy with the codebase organization as it is then I'll just close it out!
@Till Schneidereit are you feeling like it's not going to be worth the time to review (assuming a rebase)?
ah, right—I had also meant to talk about this, but forgot. I think the codebase could certainly use some amount of reorganization, but I'm personally not entirely convinced that the PR you opened is a sufficient improvement to justify the effort required. In particular given that at some—hopefully not too distant—point we'll want to make things more Rust focused, and will want to reorganize things in yet another way then
Ah reasonable -- yes the Rust experimentation PR still hasn't landed, which will cause some changes, but hopefully only to the crates
folder at the root
That said, I'm happy to close out the PR for now -- if it's not a pressing problem we've got other fish to fry
oh, the Rust PR that's currently open won't change other things, agreed. But eventually I very much would like to move StarlingMonkey from being a C++ runtime with support for Rust to being a Rust runtime with support for C++ builtins. And that should come with more a substantial reorganization
from being a C++ runtime with support for Rust to being a Rust runtime with support for C++ builtins
Definitely looking forward to that!
Last updated: Jan 24 2025 at 00:11 UTC