Issue 1283: fix interactive module reloading

[vyzo]

Closes #1283

• Fixes interactive module reloading, so that a compiled module (and all its nested modules) can be properly reloaded
• Adds load order tracking in the loader
• Adds a list-modules procedure that allows you to inspect loader state
• Fixes a deadlock in the loader caused by incorrect mutex release in reload-module!

[netlify]

✅ Deploy Preview for elastic-ritchie-8f47f9 ready!

Name	Link
🔨 Latest commit	eea8b5d
🔍 Latest deploy log	https://app.netlify.com/sites/elastic-ritchie-8f47f9/deploys/6758c3f9792c270008c55377
😎 Deploy Preview	https://deploy-preview-1284--elastic-ritchie-8f47f9.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[drewc]

c/pasta lol: After looking: Where/when does it add the "~0" and friends? Or does it not fix that part?

Or:

if you actually (reload-module! "teggot/llsp/gccjit~0") instead of (reload-module! "teggot/llsp/gccjit") it works

Does the import order deal with that? I mean, does loading the "gccijt" then load the ~0 etc so reloading that reloads those?

• drewc (Drew Crampsie)
  hates it when he can't see the solution to the problem because the problem no longer exists so does not need to be solved :P

[vyzo]

string-prefix? of the base does it.

[vyzo]

and yes of course, import order was added exactly to deal with this.

[drewc]

Looks good to me.