Where does the slow-edge list live in the class version, and why?
- A.In a global SLOW_EDGES, as in Lesson 6-2
- B.Inside the Dijkstra object as self.slow_edges, like self.blocked — it is the planner's own knowledge of the grid, reached only through add_slow_edge()
- C.Inside the harness
- D.In the Navigator
Answer Why?
Why must BFS have an add_slow_edge() method that does nothing?
- A.Python requires every class to have the same methods
- B.So the harness can call planner.add_slow_edge() on whichever planner it holds without checking which one — the same reason Manhattan has an add_blocked() that does nothing
- C.Because BFS secretly uses weights
- D.It does not; the harness skips BFS
Answer Why?