ChosunOne
ChosunOne
A workaround is to change the parser.rs file line 7 to: `use std::os::windows::ffi::OsStrExt;` and add the line: `use osstringext::OsStrExt3;` after it. This will fix the build errors but will leave...
The alternative method still doesn't build, but reintroducing the target checks in parser.rs of clap fixes the issue. We should raise an issue with clap about this.
Still working on it. Note the conspicuous lack of passing tests
I'm getting the same thing. I was able to work around it by modifying the "predict_step" method to use just the first input of the tuple before calling the forward...
I strongly recommend an exponential moving average with an appropriate decay chosen. This runs in constant time and space, and is easily tweakable for finding the right balance of recent...
@billuo I think that sounds right, the file I'm editing is on my `F` drive while neovim is on my `C` drive.