Ivan Smirnov

> @dean0x7d Regarding features: As an option, could the module namespace remain intact? I.e. import m instead of from m import *? I can see both schemes being useful under...

@dean0x7d In regards to cleaning the build folder - do you mean the cached module binaries or the temporary build artifacts (object files etc)? If it's the former, I'm not...

> That would be nice. The cache dir grows rapidly as the C++ code in the notebook is edited (as far as I understand each change of the code creates...

Another issue about cleanups I forgot to mention -- there may be multiple kernels open at the same time, so not all cached extensions may be "owned" by just one...

Is this repository abandoned?

> Hmm yeah I'm open to adding an option for it, opt-in even. Maybe we should control this via rust logging levels? Opt-in with rust log levels sounds great. (Because...

Looking forward to the version bump as well as the `ls` error is pretty frustrating.

Was trying to make it work with 2D as well, but scratching my head re: how exactly to do it... wonder, would any of you mind sharing a quick snippet?...

Same story here, if your `rustfmt.toml` / `.rustfmt.toml` has a few non-default settings (which, by the way, can be nightly-only, so you format it with `rustfmt +nightly foo.rs` or `cargo...

Just a note, unlike running cargo-clippy which immediately splits the bottom part into "Run Cargo Command" and a colored output section on the right, cargo-cranky output requires `--color always` for...