You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But I think it would be a lot more intuitive if we had flags like -m stop after monomorphization rather than before. That way, if you want to see just the monomorphized code you would do -m, instead of having to remember which stage follows monomorphization. I suggest the following:
usage: perplc [OPTION ...] INFILE.ppl
-m Stop after monomorphizing
-l Stop after linearizing
-e Stop after eliminating recursive datatypes
-c Stop after compiling to final-stage PPL code (not to FGG)
...
The text was updated successfully, but these errors were encountered:
colin-mcd
changed the title
ImprovingCommand Line Flags
Improving Command Line Flags
Feb 20, 2023
I like this idea~
I guess each stage of our compiler depends on the previous stages and there is no "optional" stage. (I could imagine replacing a stage by a check that, for instance, the input program is already linear or monomorphic.)
Usage right now is
But I think it would be a lot more intuitive if we had flags like
-m
stop after monomorphization rather than before. That way, if you want to see just the monomorphized code you would do-m
, instead of having to remember which stage follows monomorphization. I suggest the following:The text was updated successfully, but these errors were encountered: