-
```
~/dfinity/motoko $ echo '{ foo = 5 * 5 } : { foo : Nat64 };' | moc
Motoko compiler (revision 0.5.3-12-g84d34b505)
> stdin:1.1-1.16: type error, expression of type
{foo : Nat}
cannot produc…
-
So for example when I am using an RBTree, just looking at the code it looks as if everything is just stored in "memory". The tree can grow seemingly infinitely and I see no use of file systems or call…
-
-
Players have reported Thermal Elementals being pretty annoying to find, since they're biome specific and TF biomes are pretty huge, plus it's always a random chance if you're going to find one I guess…
-
@hansl asked
> Text to Blob how?
The only existing way so far is:
Take the string, iterate over `.chars()`, manually implement utf8-encoding, encode that sequence of bytes as base54, add the d…
-
Christoph says:
Oh, I don't like that omitting a type parameter defaults it to None... chasing that one down was a pain
Eg.
```
public func toArray(xs : Iter) : [A] {
let buffer = Buffer.…
-
In Motoko, we can define `type record = Nat;`, then this gets translated to `type record = nat;` in IDL. This cannot be parsed in the IDL compiler, as `record` is a keyword in IDL, but not in Motoko.
…
-
Motoko now supports actor classes as compilation units, providing access to canister arguments.
However, we need to decide how to expose the canister argument as IDL to dfx etc.
-
See: e.g.
https://github.com/purescript/package-sets/pull/749
https://github.com/dfinity/motoko-base/pull/197
https://github.com/dfinity/motoko-base/pull/199
-
The latest Candid test suite extensions show that our decoding of service and function references isn’t great (need to do stricter checking in the type table).
Shouldn’t be too hard, but is also no…