Results 273 comments of Jacob Lifshay

Luke (the person at Libre-SOC who originally encountered this bug) thinks this bug is best fixed fixed by making yosys split long carry4 chains. imho vpr and nextpnr-xilinx are where...

running `time rm -rv /sdcard/Minetest/` gave me: ``` real 5m22.694s user 0m0.400s sys 0m2.183s ``` 5min is absurdly long for

I guess a basic summary is Android 11's new sdcard filesystem is trash and we really should figure out how to work around it...

10GB used for me after initial build completed on https://salsa.debian.org/Kazan-team/kazan rls-preview 1.33.0 (9f3c906 2019-01-20) installed via rustup Linux x86_64 Note that building kazan builds LLVM as part of the process,...

@Xanewok ping. Hoping this will be set to the default soon at least on linux, I'm getting out-of-memory with RLS even though I have 32G of memory.

by manually adding the signatures to the docstrings, pyls can autocomplete all the methods. See https://github.com/PyO3/pyo3/issues/310#issuecomment-556038749 for a proposal

> Does that include type annotations or is that too much to ask? From what I understand, type annotations don't work at all for return types (CPython doesn't recognize the...

> I do like this new syntax for `#[pymodule]` very much, and would be happy to go down that road. How would you propose classes and attributes to be added...

> I'm sorry I noticed `#[proc_macro] mod m { ... } ` is unstable today([rust-lang/rust#54727](https://github.com/rust-lang/rust/issues/54727)). It's stable (in the latest releases): [rust-lang/rust#64273](https://github.com/rust-lang/rust/pull/64273) What's unstable is non-inline `mod`: ```rust #[my_proc_macro] mod...

> > just use the name that the use statement introduces > > Another idea: How about removing the whole `use` statement? I would leave the `use` statement in there...