Hi i am looking to get the cleaned data set for https://github.com/happynear/FaceVerification at
http://pan.baidu.com/s/1hrKpbm8
no password listed as far as i can see. Thanks!
u/actuallyzza
Hi i am looking to get the cleaned data set for https://github.com/happynear/FaceVerification at
http://pan.baidu.com/s/1hrKpbm8
no password listed as far as i can see. Thanks!
I've run into a case where borrow checker seems to think that returning from a function mid loop can result in a mutable borrow being held over into another iteration of a loop.
I've put together a simplified example. The curious part is in the lastfn, the rest is just fluff to justify the signature.
How I mentally check borrows in loops is to figure out what borrows survive over a loop iteration after the drops at the end of the scope occur and make sure that no incompatible borrows occur. In this case we can see that the candidate reference to be returned gets dropped
Yesterday u/sepease asked discussion provoking question about how to process a file gradually and produce a stream to be returned in an actix-web response.
One of the nicer APIs taking shape is the tokio-fs File type, however that limits usability due to a lack of AsyncRead equivalents to std::io::BufReader although they should be coming one day.
To get around this I had a crack at writing a blocking aware version of poll_fn to allow easy creations of streams while still using the std library File and io types, or other blocking closures.
Would someone familiar with tokio be able to comment on whether the following would work as expected? That is blocking file IO shifted to the blo
I'm looking for any rust facilities to achieve CPU Dispatch or function multiversioning (attributes in source, cargo, asking rustc/llvm politely). Ideally it would be possible to do this at a crate level, but if it can be done per function or per binary that would also be interesting to me.
I'd like to ensure a crate produces multiple specialized versions when compiled for certain targets. e.g. compiling for x86_64 will produce versions for Core2, SandyBrid
Hi, so I've put together a small barrier library to allow synchronization with the completion of work submitted to threads or threadpools. It's been an excuse to get ankle deep in the hairier side of rust, and also to provide a solution to this issue which doesn't potentially deadlock the threadpool. I'm primarily looking for feedback on correctness (unsafe, atomic ordering and drop/panic interactions) and improvements to tests, but also great would be help with naming(I don't know if this type of barrier has established naming conventions or
You've reached the end of this feed.