Joachim Breitner
Joachim Breitner
Well, it should probably be caught by the type checker. Shouldn't it give a capability error (or whatever the name of our implicit type parameters for await contexts are)?
Thanks for the report! NB: `simp` doesn't seem to actually need the `h`, maybe that’s part of it? ``` variable (α : Type) def sample (n : Nat) : Nat...
This seems to be not about `decreasing_by` but the pattern match completenes checker, so probably worth its own report.
I think only `Int`. Surely not `~` without all the other bitwise operations (category B in https://sdk.dfinity.org/docs/language-guide/language-manual.html#syntax-ops), right? (Although right rotation doesn’t make sense for `Int`)
We'd be facing the same problems as for `debug_show`, so the best thing we can do right now, I think, is add these as their own AST form. I would...
Related: * c6e0ea6df62c3d94f1cadb02a48a6b9f6d7a36ab (exposing this as `prim …`) * https://github.com/dfinity-lab/motoko/issues/1655 (thoughts about how to expose this as functions) * the discussion around non-parametric polymorphism (no issue yet, I think)
So maybe the title could be “feat: structure syntax in mutual datatype definitions”
Just based off the PR description: did you consider the alternative of making all motives implicit? Or is there a good reason to make them explicit it some cases?
Thanks, these are good points. Ah, and I should have followed the link to the issue to find it out myself :-)
> Note: the test case added by the above commit uses simp and not simp_all. Could that be why the bug is not caught by the CI tests? Ah, I...