Hint for Galois Field doesn’t parse

[gitonthescene]

FWIW, this is what I get from running the WASM version on an iPhone running iOS 15.1:

[gitonthescene]

There’s also a typo later on. I’m not sure if that’s worth a separate issue:

As you see, native sort is trendously faster, since it is using a very efficient sorting implementation.

It should be “tremendously”. I’ll post a pull request when I’m in front of my desktop.

[gitonthescene]

Also the tutorial now has an example of cut ^ so perhaps it should have a bullet at the bottom.

[gitonthescene]

I should also mention I found tutorial extremely well written. Thanks so much for doing this.

[kelas]

I should also mention I found tutorial extremely well written. Thanks so much for doing this.

thank you. yes, some people say it is quite a sweetheart.

sadly, as you can clearly see, it is a perpetual WIP.

thanks for stopping by.

[kelas]

Also the tutorial now has an example of cut ^ so perhaps it should have a bullet at the bottom.

oh, right. could you be bothered to pr a fix?

[kelas]

There’s also a typo later on. I’m not sure if that’s worth a separate issue:

As you see, native sort is trendously faster, since it is using a very efficient sorting implementation.

It should be “tremendously”. I’ll post a pull request when I’m in front of my desktop.

my command of your language fails me all time time.

[kelas]

FWIW, this is what I get from running the WASM version on an iPhone running iOS 15.1:

it is a bit of an easter egg :) ascii cast is possible. see if you can figure it out, and suggest a fix :)

[gitonthescene]

Sure. I’ll post fixes hopefully later today.

[kelas]

Sure. I’ll post fixes hopefully later today.

please also note that wasm build at kparc.io/k is ancient. i recommend using official builds

[gitonthescene]

I still haven’t grokked it yet but changing the final flip to an each makes it work.

FWIW, this type is not discussed in the tutorial:

 @2\32 458 1172 1443 275
`LI
 @+2\32 458 1172 1443 275
`LI

I'm assuming this hint used to work.

P.S. My battery life is a proxy for seeing how many tries it took. :D

[gitonthescene]

Sure. I’ll post fixes hopefully later today.

please also note that wasm build at kparc.io/k is ancient. i recommend using official builds

FWIW, I had issues with the npm install which I noted here.

[kelas]

Sure. I’ll post fixes hopefully later today.

please also note that wasm build at kparc.io/k is ancient. i recommend using official builds

FWIW, I had issues with the npm install which I noted here.

issues with the npm install

sadly, this one is above our head. it is used to work very well, note the past tense.

the time has come to decommission it, thanks for the heads up.

[kelas]

Sure. I’ll post fixes hopefully later today.

please also note that wasm build at kparc.io/k is ancient. i recommend using official builds

would you like to join the conversation on kparc.slack.com?

[gitonthescene]

Sure. I’ll post fixes hopefully later today.

please also note that wasm build at kparc.io/k is ancient. i recommend using official builds

would you like to join the conversation on kparc.slack.com?

Very much so. Thanks.

[gitonthescene]

would you like to join the conversation on kparc.slack.com?

Very much so. Thanks.
I wasn’t able to log on with that link alone. Is there a way for me to reach out somehow for access?

[gitonthescene]

would you like to join the conversation on kparc.slack.com?

Very much so. Thanks. I wasn’t able to log on with that link alone. Is there a way for me to reach out somehow for access?

@kelas Is the google group the right place to follow up on this?