| 48 | | * P1 what happens to TH code? see dynbrk5 test |
| 49 | | |
| 50 | | * P1 wrong variable names (see below- why is this still happening?) |
| 51 | | |
| 52 | | * P2 let you go back in time - save the last N breaks. (maybe only with a flag, otherwise slow). |
| 53 | | |
| 54 | | * P2 when an exception is thrown, behave like a breakpoint. |
| 55 | | |
| 56 | | * P2 tabs go wrong with :list |
| 57 | | |
| 58 | | * P2 Support Unicode in data constructor names inside info tables. Actully this should just be a matter of using the underlying fast string in the occname. (MODERATE) |
| 59 | | |
| 60 | | * P2 Use a primop for inspecting the STACK_AP, rather than a foreign C call. (MODERATE) |
| | 50 | * P2 :force should catch exceptions, so [1,2,undefined] would display as `[1,2,< exception >]` |
| | 51 | |
| | 52 | * P2 sometimes the result types are wrong (see result001 test) |
| | 53 | |
| | 54 | * P2 when showing a SrcSpan, we could say which top-level function contains it. Ideally we should store the declPath that |
| | 55 | the coverage pass collects, but as a [OccName] rather than [String]. |
| | 56 | |
| | 57 | * P2 perhaps we should have a :watch command, that could be used to save variables for future inspection (they wouldn't get |
| | 58 | thrown away by :continue) |
| 64 | | * P2 Improve :list command: add ':list f', ':list M 23', etc. |
| 65 | | |
| 66 | | * P2 The delete command. It is fairly primitive, and probably not done in the best way. This will be fixed when the API is finalised. (EASY) |
| 67 | | * P2 ":delete 999" doesn't complain |
| 68 | | |
| 69 | | * P2 Allow breakpoints to be enabled and disabled without deleting them, as in gdb. (EASY) |
| 70 | | |
| 71 | | * P2 Extend breaks and step with counters, so that we stop after N hits, rather than immediately. (EASY/MODERATE) |
| | 62 | * P2 We can disable a breakpoint with ":set stop N :continue", but this still prints out the breakpoint info when we stop. |
| | 63 | Should we print the info only if there were no commands? |
