SasakiSaki

This feature should be able to merge, any update?

It looks like all gc types declarations are supported. Can we create an issue to track the progress of the gc proposal, such as - gc instruction support - non-collection...

The parsed result is: ```yaml Html { errors: [], quirks_mode: NoQuirks, tree: Tree { Fragment => { Element() => { Element() => { Text(Tendril(owned: "Hello, world!")) } } } },...

Report as io error is indeed an abuse. The main use should be to output the location of the call site, what information to give is up to the user....

I added a basic support in #1903. Png is not always available, so I added a type field to safely convert the byte stream to the corresponding type

I'm not familiar with bytemuck, is there an interface to cast `Vec` as `Option>`?

Where can I download pre-built jars? I don't know how to build a specific branch version.

Thank you very much for your information, I improved part of the implementation based on wob. I have another question, I want to know how the trait should be implemented?...

Okay, thank you for your answer, I have no more doubts

@segeljakt I created a test case here, the content after juxtaposition will be discarded. https://github.com/oovm/wolfram-parser/blob/1d848b9f763da50b5a3712d0a930a591ea3259c8/projects/wolfram-parser/tests/main.rs#L10-L41 This is the implementation part of pratt parser: https://github.com/oovm/wolfram-parser/blob/1d848b9f763da50b5a3712d0a930a591ea3259c8/projects/wolfram-parser/src/parser/from_str/parse_expr/mod.rs#L22-L87