docs: update legal compiler input

[antalsz]

Description

The documentation describing "Legal compiler input" was outdated. This PR fixes it to describe what I believe is currently the case.

Checklist

• The PR targets the master branch
• The above description motivates these changes.
• The change is atomic and can be described by a single commit (your PR will be squashed on merge).
• All changes to code are covered via unit tests.
• Parameters and return values have type hints with PEP 484 syntax.
• Functions and classes have useful Sphinx-style docstrings.
• (New Feature) The docs have been updated accordingly.
• (Bugfix) The associated issue is referenced above using auto-close keywords.

[github-actions]

Bencher Report

Branch	modernize-legal-compiler-input
Testbed	ci-runner-linux

⚠️ WARNING: No Threshold found!

Without a Threshold, no Alerts will ever be generated.

• Latency (nanoseconds (ns))

Click here to create a new Threshold
For more information, see the Threshold documentation.
To only post results if a Threshold exists, set the --ci-only-thresholds flag.

Click to view all benchmark results

Benchmark	Latency	seconds (s)
test/benchmarks/test_program.py::test_copy_everything_except_instructions	📈 view plot ⚠️ NO THRESHOLD	10.38 s
test/benchmarks/test_program.py::test_instructions	📈 view plot ⚠️ NO THRESHOLD	4.00 s
test/benchmarks/test_program.py::test_iteration	📈 view plot ⚠️ NO THRESHOLD	4.05 s

🐰 View full continuous benchmarking report in Bencher

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
7308	6421	88%	87%	🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 25ba8c4 by action🐍