Attention une mise à jour du service Gitlab va être effectuée le mardi 14 décembre entre 13h30 et 14h00. Cette mise à jour va générer une interruption du service dont nous ne maîtrisons pas complètement la durée mais qui ne devrait pas excéder quelques minutes.

Commit 61019779 authored by POTTIER Francois's avatar POTTIER Francois
Browse files

TODO.

parent 4683000f
...@@ -16,18 +16,12 @@ ...@@ -16,18 +16,12 @@
* Move more of ErrorReports from CompCert to MenhirLib. * Move more of ErrorReports from CompCert to MenhirLib.
In [show], might want to apply [shorten] to the output of [f]. In [show], might want to apply [shorten] to the output of [f].
* Implementing may_reduce by looping over the action table may be too
conservative? There may be situations where there is no reduce action
in the table (because they were killed off by conflict resolution) yet
this state is still capable of reducing this production.
* clean up this TODO file! and use gitlab issues for known bugs. * clean up this TODO file! and use gitlab issues for known bugs.
* Contribute ocamlbuild rules for dealing with .messages files. * Contribute ocamlbuild rules for dealing with .messages files.
* see if --only-preprocess-for-ocamlyacc could be implemented. * Complete the implementation of --only-preprocess-for-ocamlyacc.
Re-introduce $1 keywords. Currently, the position keywords ($startpos, etc.) are not supported.
Define $startpos, etc.
* The documentation says not to use _i, * The documentation says not to use _i,
but --only-preprocess produces it. but --only-preprocess produces it.
...@@ -154,8 +148,6 @@ ...@@ -154,8 +148,6 @@
(see e.g. belloeil.mly) (et le reduced_parser.mly d'Adrien Guatto) (see e.g. belloeil.mly) (et le reduced_parser.mly d'Adrien Guatto)
(also check the parser.mly sent by Andrej Bauer on 2016/01/21) (also check the parser.mly sent by Andrej Bauer on 2016/01/21)
Or just give up on explaining the conflict in this case. Or just give up on explaining the conflict in this case.
Take priorities into account *during* the construction of the
automaton? Is it feasible? Compatible with Pager?
* BUG: cutdown.mly * BUG: cutdown.mly
......
...@@ -93,3 +93,8 @@ for now. ...@@ -93,3 +93,8 @@ for now.
What should we do about it? What should we do about it?
Note that the incremental API may allow reaching some states that LRijkstra Note that the incremental API may allow reaching some states that LRijkstra
would declare unreachable -- so, be careful. would declare unreachable -- so, be careful.
* Implementing may_reduce by looping over the action table may be too
conservative? There may be situations where there is no reduce action
in the table (because they were killed off by conflict resolution) yet
this state is still capable of reducing this production.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment