☂️ Internal Tooling

[NicholasLYang]

Description

Internal tools are helpful for both the Rome core team and for other contributors. They let people gain an understanding of our various data structures; they facilitate debugging and bug reporting; they help with comparing to other tools. They're also great because they're (relatively) easy to make without too much knowledge of the codebase.

That said, we shouldn't devote too much time to internal tooling, as we do need to ship the actual product, and internal tooling can be a great way of procrastinating that actual work.

My hope is that by documenting potential internal tooling tasks, contributors can potentially take them over.

• 📎 Diff mode in Playground #2617
• 📎 Generated playground links for tests #2618
• 📎 Split playground run function #2619
• 📎 Tiling Views #2620
• 📎 Search in Tree Views #2621
• Write a tool for helping debug rome_ir #2587
• 📎 Native Playground #2622
• Add code mirror plugin #2984
• New tab in the playground to show lint diagnostics #3010

[github-actions]

This issue is stale because it has been open 14 days with no activity.

[MichaReiser]

Closing, we can track the code mirror plugin in it's own issue.