modulus

Hypothetically? Maybe, but it seems extremely unlikely. Even if the referendum would have run normally back then, what would have happened next?

In fact, the declaration of independence lasted seconds, because anyone who knows anything can realise the extreme infeasibility of a unilateral declaration and all it would entail.

that said, if the Spanish state is so fragile a vote could split it, then it should probably split.

I would expect that, but I'm not just talking right wingers. I personally know Sumar voters who said they will now vote for cannabis party or any random thing because of the amnesty.

Not that hard left (I gave money to Sumar but I'm realistic that it's the best we can get, more than what we want).

I know some people who are really pissed off about the amnesty, and personally I don't get it. Like in what world is the personal fate of a few hundreds of people who, let's say for the sake of the argument, ran an illegal referendum, more important than labour rights for everyone?

I played it and enjoyed it. The first time round I didn't really know what I was doing in terms of game mechanics, just went by what I would do in that place, and my moderation speed fell to 0 so I lost.

Second time I managed to finish the game, with some compromises but not too awful.

Possibly yes. I'll check if the results are equivalent.

Apparently the problem is due to an incompatibility between the use of certain libraries (winapi and windows-sys) which use different versions of COM. At least so I deduce from the documentation I've read.

There's a workaaround:

On Cargo.toml, use.

[build-dependencies]
embed-manifest = "1.3.1"

And on the root of the project (not the src dir) create a build.rs file with the following content:

use embed_manifest::{embed_manifest, new_manifest};

fn main() {
    if std::env::var_os("CARGO_CFG_WINDOWS").is_some() {
        embed_manifest(new_manifest("Contoso.Sample")).expect("unable to embed manifest file");
    }
    println!("cargo:rerun-if-changed=build.rs");
}

This embeds a manifest together with the executable, solving the issue.

Same erro by using this approach.

Tokio works fine, by itself. windows-native-gui works fine, by itself. It is the combination that causes this issue.

The way I look at this is I have a reasonable understanding of rust. I'm not an expert but I can more or less do whatever computation I need to do, use crates, and so on. But with async it's like learning another language. Somewhat of an exaggeration, but it's not just what code you need to write, but also being able to read the error messages from the compiler, understanding the patterns and so on. So yes, it's probably fine, but it does take work.

There is literally no instance in which expanding the scope of copyright law is a good thing. Never.

Not saying this won't have any negative effects on people, however I think it's a little premature to guess at what it will be like. About 3/4 of the article is commenting what it will do to men when we find out only at the end women are the majority of users.

So probably the tokio mpsc channel, right? Why is it not possible tu use normal sync channels? I've read about it but I don't understand the reason.

Also I'm thinking of spawning a thread to do this part, or should it run on the tokio main function?

I've had just this case. Wanted to use a particular crate that uses async and it's forcing me to do lots of async things I'm unfamiliar with. I resent it a little, especially for a program that I'm fairly sure will not require concurrency of this sort.

At the same time, maybe I'll get used to async rust if I use it enough. But so far I'm not having a lot of fun with it.