lolbinarycat
lolbinarycat
> I think this is a duplicate of #1164. it is not. that issue is for any event, this issue only applies to all-day events. although both seem to step...
another important thing to consider is crates that provide futures for io, and launch a background thread in order to Wake those futures, notifying the executor when they can make...
my interpretation (mostly informed by reading `std::thread`) is as follows: 1. if it calls Future::poll, it's an executor 2. if it calls Waker::wake after a future returns Pending, it's a...
@lbernick you wrote the relevant paragraph, mind weighing in on this?
i'm just asking what you meant when you wrote that words i'm really not sure who else *could* weigh in on this.. i guess it becomes an issue of prescriptivism...
We also ran into this in rustdoc with the following `package.json`: ```json { "dependencies": { "browser-ui-test": "^0.20.6", "eslint": "^8.6.0", "eslint-js": "github:eslint/js" } } ``` Which led to this terrifying message...
what do people think about using [upx](https://upx.github.io/) to create statically linked files?
> Seems silly to only statically link for people who install that? what do you mean? upx isn't like snap or something, it produces plain executables that have no dependencies....
it's self-extracting.