Christoph
Christoph
Related to https://github.com/dfinity/motoko/issues/966 Should we consider that issue closed by this PR, or could we at least use it as an opportunity to define a list of operations we'd like...
I'd prefer to have the content type be part of the import URI, similar to what Claudio proposed. That wouldn't require special casing in the type checker and allow tools...
@ggreif Can we call this one fixed in https://github.com/dfinity/motoko/pull/5013?
Could we amend the example here to include the definition of `foo`, as I think it's required to produce the problematic error here?
This issue is probably long outdated with all of the documentation revamps that have happened in the last 5 years. Anything worth keeping this open for here @crusso?
Wouldn't it be easier to directly use `test/run.sh` in those cases? ```sh test/run.sh test/run/example.mo # Run `example.mo` test/run.sh test/run/example.mo -a # Run and accept output for `example.mo` ```
Pretty sure this ship has sailed. Candid records/variants use hashes as field names. @crusso Good to close?
`[email protected]` switches from `base` to `core`. As this code is running `base`s test-suite it should probably stick to `[email protected]`.
> Instead of using a global cache that needs to be reset carefully, how would you feel about passing the relation argument as the intial argument to decodeValue, along with...
I'll set up some benchmarks before trying to think too hard about what's fast or slow here... Thanks for the review I think we're good to merge for now.