Issue #21 brings up the requirement that --show-asr really must be completely unambiguous. = might mean Eq or it might mean Eqv or Assignment? Any kind of operator notation like that must be replaced with either a symbol like Assignment or must be explicitly written in ASR.asdl.
Secret sugar like operator synonyms or multinyms hidden in the C++ implementation of ASR make MASR's ADSL back-channel really difficult!
As we move toward greater formality for MASR, it's important that --show-asr be unambiguous, explicitly written in full in ASR.asdl, and context-free. Leave the sugar to MASR! Don't make MASR do dispatch-on-type or lookahead on the printouts from --show-asr!
Issue #21 brings up the requirement that
--show-asrreally must be completely unambiguous.=might meanEqor it might meanEqvorAssignment? Any kind of operator notation like that must be replaced with either a symbol likeAssignmentor must be explicitly written in ASR.asdl.Secret sugar like operator synonyms or multinyms hidden in the C++ implementation of ASR make MASR's ADSL back-channel really difficult!
As we move toward greater formality for MASR, it's important that
--show-asrbe unambiguous, explicitly written in full in ASR.asdl, and context-free. Leave the sugar to MASR! Don't make MASR do dispatch-on-type or lookahead on the printouts from--show-asr!