fix: uses correct comment syntax for comments on design justifications
This commit is contained in:
parent
764e335364
commit
e38932a3e8
@ -115,15 +115,14 @@ object parser {
|
||||
((`<pair-elems-type>` <**> `<array-type>`)
|
||||
.map(arr => (_: UntypedPairType) => arr) </> identity))
|
||||
|
||||
/** Statements
|
||||
*
|
||||
* Atomic is used in two places here:
|
||||
* 1. Atomic for function return type - code may be a variable declaration instead, If we were
|
||||
* to factor out the type, the resulting code would be rather messy. It can only fail once
|
||||
* in the entire program so it creates minimal overhead.
|
||||
* 2. Atomic for function missing return type check - there is no easy way around an explicit
|
||||
* invalid syntax check, this only happens at most once per program so this is not a major
|
||||
* concern.
|
||||
/* Statements
|
||||
Atomic is used in two places here:
|
||||
1. Atomic for function return type - code may be a variable declaration instead, If we were
|
||||
to factor out the type, the resulting code would be rather messy. It can only fail once
|
||||
in the entire program so it creates minimal overhead.
|
||||
2. Atomic for function missing return type check - there is no easy way around an explicit
|
||||
invalid syntax check, this only happens at most once per program so this is not a major
|
||||
concern.
|
||||
*/
|
||||
private lazy val `<program>` = Program(
|
||||
"begin" ~> many(
|
||||
|
Loading…
x
Reference in New Issue
Block a user