Sven

> ```rust > use once_cell::sync::Lazy; > use scraper::Selector; > > macro_rules! selector { > ($e: expr) => {{ > static SELECTOR: Lazy = Lazy::new(|| Selector::parse($e).unwrap()); > &*SELECTOR > }}; >...

Here is a MVP: https://github.com/SirWindfield/scraper-proc-macro. Compilation fails for one of the tests as the proc-macro panics due to a wrong formatted selector string.

The better approach would probably be to define error types in `scraper` itself and export those.

No

The author hasn't been on GitHub for more than a year now. Sad that such useful crates kind of get lost. Do other people than @whatisinternet have push access (and...

No problem! IIRC it should actually work out of the box :) And good luck with your thesis :)

Hey! Is it OK if I tackle this one down on Saturday? 🤔

> Something I have seen before is introducing special `INDENT` and `OUTDENT` tokens in your lexer. I thought that was quite clever. Yep, that's how I've seen a lot of...

Does this imply being able to do something like this? ```rust fn parse() -> impl Parser {} ```

I found [this](https://github.com/jruere/multiprocessing-logging/issues/9#issue-250356206) issue today and tried it out. It didn't work for me. I pass `install_mpl_handler` as he/she did. I created a MWE [here](https://github.com/SirWindfield/multiprocessing_logging_mwe). The weird thing is though,...