Posting the error here for easy viewing:

Run ./roc_nightly/roc build ./examples/env.roc

thread '<unnamed>' panicked at 'Ability specialization is unknown - code generation cannot proceed!', crates/compiler/mono/src/ir.rs:5829:30

Let's see if this error still occurs...

The error still occurs but is more specific now:

thread '<unnamed>' panicked at 'Ability specialization is unknown - code generation cannot proceed!: NoTypeImplementingSpecialization', crates/compiler/mono/src/ir.rs:5788:10

@ayazhafiz any idea what this error might be referring to?

Is this a new error on this branch, or is this happening without the changes here as well?

The problem is that if we don't know what type to generate an ability specialization for, we cannot generate code (this is the "evil ability" pattern). Why that would be happening on this branch is not clear to me, unless the exposes types are having glue generated for them or something.

This only occurs with the changes here, could it be that the glue code needs to be updated?

Ok, so probably glue is picking up the exposed types in EnvDecoding and attempting to generate code for them, which is a problem, since those types are not material until their ability variables are instantiated.

I can reproduce the error CI is getting locally by:

1. Checking out the add-exposes branch of basic-cli locally
2. Doing roc build examples/env.roc

It doesn't reproduce on the main branch of `basic-cli'.

@ayazhafiz maybe it has to do with platforms as opposed to applications, rather than glue vs build?

Closing in favor of #28