Ryan Vandersmith
Ryan Vandersmith
Yeah, that doesn't look right, haha. I'll take a look at this when I get a chance after ETHDenver.
Great suggestion! I'm currently trying to maintain consistency with the Prettier ecosystem (https://github.com/prettier/prettier/issues/5755), although it seems totally reasonable to have this as an optional feature.
Transcribed from a Google Doc to track our progress with the code formatter. Open-source contributions are welcome!
Good idea--I'll look into combining this with #58 as an optional feature.
Thanks for pointing this out! I opened a PR to fix the `Array.take()` warning for the next base library release. I'll also bring the other warning message to the attention...
Makes sense, +1.
Yep, this already works as shown! I had to limit the number of imports, though: [CI output](https://github.com/dfinity/motoko-base/actions/runs/3577212012/jobs/6015947245)
It looks like we can add everything except (at least one of the) `Experimental` modules. Seems reasonable to either include or exclude all of them for consistency.
> Instead of relying on Lib.mo, we could, perhaps, extend this to profiles JS.mo (JS playground) Wasi.mo (wasmtime) and IC.mo and maybe use the default Lib.mo for a least common...
Makes sense. It also seems reasonable to defer this functionality to a third-party library, similar to Rust's `rand` crate.