I think it would be straightforward to add something to Check Syntax that reported unreachable code and that seems pretty cool and useful for TR. So CS could report any code that TR could prove was unreachable and yet the code came from the original program. I guess if John had seen that showing up in his program it might have prompted him to figure out what the bug was?
Robby On Tue, Jul 12, 2016 at 4:13 PM, Matthias Felleisen <matth...@ccs.neu.edu> wrote: > >> On Jul 12, 2016, at 5:07 PM, Sam Tobin-Hochstadt <sa...@cs.indiana.edu> >> wrote: >> >>> >>> 2) Is there some nice user interface that we could use to make the warnings >>> visible to the case of the user? Maybe a “I think I have a bug, can I see >>> the compilation warnings” button? >> >> I agree -- I think we need a better story generally for warning UI in >> Racket, but I don't know what the right solution is. > > > [Sorry John, I overlooked your questions.] > > > Instead of watching warnings scroll by in some widget, I’d rather see the > coloring solution for testing from the teaching languages adapted to TR. > > At a minimum, I could see two colors: > > RED: you’re typed. Blessed. You’re wonderful. > BLUE: you’re bad. Untyped. My propositions hate you. > > Or something like that. I could see the use of four or five colors even. But > starting with two would be a _good thing_. > > More brainstorming ideas? > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
