Giovanni Zaccaria
Giovanni Zaccaria
That's not an error. Those are local labels and NASM doesn't need the colons.
You should probably separate the parser state from the iterator state. ```rust struct FilmParser { html: Html, foo_selector: Selector, } struct FilmIterator Iterator for FilmIterator
I will close this one, because the solutions provided work
It looks like a bug in the `extract()` function, probably in the way order it processes stuff. If it matches numbers before sums, it will consider the `+` sign as...
Btw, `main()` would really benefit from using argparse. ```python def main(): parser = argparse.ArgumentParser( prog="matlab_parser", description="Parser of matlab code", ) parser.add_argument("--startLine", type=int, default=1) parser.add_argument("--endLine", type=int, default=None) parser.add_argument("--indentWidth", type=int, default=4) parser.add_argument("--separateBlocks",...
```html Hi Bye ``` parses into the following tree: ``` Fragment └── Element() ├── Text("\n ") ├── Element() │ ├── Text("\n ") │ ├── Element() │ │ └── Text("Hi") │...
Of course, don't worry. For anything just write. By the way, the code I gave you is tested, so it should work.
Since this issue seems solved, I will close it.
The idea of a macro is indeed interesting, I will leave this issue open in order to remember it. @cfvescovo
#53 is interesting because it explores the idea of a proc-macro. I think that, if it worked, it could be a cleaner solution than what we have right now. In...