Max Brunsfeld 9a198562e0 Treat parse conflicts as errors in grammar compilation ... For now, only reduce/reduce conflicts w/ no tie-breaking precedence are treated as errors. The rest are dropped, because shift/reduce conflicts are currently very common because we don't have a way of specifying associativity along w/ precedence.		2015-03-15 20:31:41 -07:00
..
action_takes_precedence_spec.cc	Treat parse conflicts as errors in grammar compilation	2015-03-15 20:31:41 -07:00
build_conflict_spec.cc	Treat parse conflicts as errors in grammar compilation	2015-03-15 20:31:41 -07:00
build_parse_table_spec.cc	Identify fragile reductions at compile time	2015-02-21 15:11:03 -08:00
first_symbols_spec.cc	Move {Syntax,Lexical}Grammar into separate files	2015-01-14 21:10:41 -08:00
get_metadata_spec.cc	Make descriptions more consistent in compiler specs	2014-09-09 13:01:18 -07:00
item_set_closure_spec.cc	Store parse items' list of consumed symbols	2015-02-20 22:53:27 -08:00
item_set_transitions_spec.cc	Store parse items' list of consumed symbols	2015-02-20 22:53:27 -08:00
lex_item_spec.cc	Move {Syntax,Lexical}Grammar into separate files	2015-01-14 21:10:41 -08:00
merge_transitions_spec.cc	Refactor - represent char sets in terms of inclusions and exclusions	2014-08-23 14:25:45 -07:00
rule_can_be_blank_spec.cc	Move {Syntax,Lexical}Grammar into separate files	2015-01-14 21:10:41 -08:00
rule_transitions_spec.cc	Remove implicit CharacterRange constructors	2014-08-23 14:52:44 -07:00