CohenArthur

Also it would be nice to have the exact details on the error. This error means that the OS couldn't create a file, because the path input is not valid....

We *think* it's the only reason but haven't tried. There might be more to it. If you have a windows build available, feel free to try. I'll add it to...

True, symlinks aren't always created. The code calling `disk::symlink()` is [here](https://github.com/Skallwar/suckit/blob/16a5ed9cf73cc3446822e0b6c654219ea3c81abc/src/scraper.rs#L131)

Oh my bad, sorry about the confusion. Any page downloading PDFs basically, so a page like https://dl.acm.org/doi/book/10.1145/3368274 is good.

> They can be exhaustive enums because support for more variants is unlikely and necessarily requires code changes anyway. Isn't the same true for `e_type`? I don't think that many...

> I see, yes I did misunderstand. What's your reason for suggesting `#[repr(u8)]`? Ah right, sorry, that wasn't very clear! I thought about using `repr(u8)` (or rather, u16) in order...

In the end the enum would be exactly as you mention: ```rust enum Type { None, Rel, Exec, Dyn, Core, OsSpecific(u16), } ``` (And this cannot be made repr(u16), obviously).

Ah, very good point. I'll add the feature to the original comment

Another similar error: ```rust mod foo { #[macro_export] macro_rules! bar1 { () => {}; } macro_rules! bar2 { () => {}; } } fn main() { bar1!(); bar2!(); // {...

Hey @omac777, thanks for the info and the research that went into this :) I'm a little unsure as to what you'd like us to do - do you want...