Guide - How to efficiently navigate and explore program code
Viir opened this issue · comments
Finding in the conversation at #34 (comment):
User 'scrolled down' to search for relevant portions in the program code.
This approach for navigating does not scale well to larger programs. Following semantic references reduces the time to discovery:
Write a guide on how to use code navigation. Use the linked conversation as a checklist if concrete examples are covered.
Dependencies
The VSCode variant of the IDE setup already has navigation via references already implemented for both directions. Explore adding this functionality to the new default IDE too. The constraints in the PL (no polymorphism, shadowing, overloading) might make this simple.
Related roadmap item
Long-term, dynamic view and navigation on an application scenario seem better suited than a static view of the program code. One advantage will be removing branches that are dead in that scope which in turn reduces distractions.