-
This operation has led to numerous time-space issues for folks (often running out of cycles when they hope not to).
In general, we should not provide operations with nice APIs (in terms of types) t…
-
### Motivation
Currently, polymorphism is fully parametric and erased in Motoko. Consequently, values of variable type cannot be used in any of the operations that requires intensional polymorphism…
-
I stumbled upon this project while trying to find a solution to run javascirpt on DFINITY(dfinity.org). To do so I need a wasm module that I can define a .did file for. Given these two things I shou…
-
Tests below are in run-drun/ directory, but they're not run with drun or ic-ref so they either not need to be in drun/ or the test configuration is buggy and they're incorrectly skipped.
- actor-cr…
-
The Motoko StableMemory libraries bother me since they allow direct access to stable memory, using absolute addresses, are non-modular and will prevent us from moving to a better world where stable va…
-
The idea is that this would prevent sending/awaiting from within exp (and the concurrency issues this raises due to interleavings) and would be useful for enforcing atomic sections of async method bod…
-
#### Problem
Despite having a deprecated status, `Array.append` continues to be used in new Motoko code by IC developers. In nearly all cases, these uses are inappropriate, and the array should in…
-
Now that we got access to a runtime candid subtype check (#3171), we could consider using it to perform a dynamic and atomic (!) type safety check on upgrade.
By storing the candid interface in th…
-
@matthewhammer @crusso
I've recently moved from doing local testing to main network testing, and one of the large difference between testing locally and on the main network are limitations such as…
-
This a sketch how we might support abstraction of asynchronous code without compromising the "always" commit semantics of `await`, unlike previous proposals (https://github.com/dfinity/motoko/issues/1…