A github issue to track this would be appreciated @nomiskatz
OK; I’ll do that late today, or maybe tomorrow. Would you prefer a single GitHub issue to cover all three points, or separate issues?
actually since you have fixes, can you go ahead and make PRs? minimal change + a changelog entry would be great. Thanks.
Sure, if my changes are good enough. (But what about tests?)
Oh, should I create a PR to make lambdaisland.tools.namespace.repl/remove-disabled public?
Kaizen, lots of small improvements is what open source is built on. Don't break existing tests (obviously). If you can add tests for changes/additions then that's great, if you don't but the change seems reasonable and you've tried it out then that's fine too.