Alessandro Coglio
Alessandro Coglio
The latest Leo lexer still uses `is_ascii_whitespace`, so the discrepancy still exists. I believe that we should follow the grammar and disallow form feed. While we are at it, I...
This is no longer relevant, because the logic for counting lines has been moved outside of the tokenizer, in the `span` crate.
This issue is still relevant. We need to make a decision, also because currently there is a discrepancy between the grammar's notion of line terminators and the span file analyzer's...
This issue is still relevant, even though [the code](https://github.com/AleoHQ/leo/blob/1ccdb3311fdc9d7eacbadb58fce4a362ec572249/compiler/parser/src/tokenizer/lexer.rs#L304) has changed since this Issue was opened.
I've updated the grammar rules listed above with the current ones. I think that this Issue could be still relevant to discuss, but I'm closing because it doesn't seem too...
Superseded by https://github.com/AleoHQ/welcome/pull/222.
Should we merge this?
I think this is a good proposal, and I'd be happy to add `:code-source` information to XDOC topics that don't reside in the same file as the code they document.
The proposed (and already supported) syntax seems appropriate. I'm expecting that the inlining of bounded recursion will take place alongside the other "flattening" transformations -- loop unrolling, constant propagation/folding, etc....
@moAlobaidi @aharshbe Thank you for helping to track this down. (And no, I don't know the definitions; I opened this issue both to get the doc improved and to understand...