Joe Politz

Typically we haven't reported binding errors for shadowing across namespaces. Pyret has three – values, types, and modules (and arguably datatypes but that's basically just types). So you can bind...

@blerner do we want to spec this as an error? I could go either way. It's not technically backwards compatible with code written since module system updates.... but also I...

Both of those are super misleading as “just” identifiers in algebra notation, and are things a student or teacher might write expecting an operation to happen. I think this is...

Agreed. Filing under “just because we can, don't”

Thanks! A few tests here would help make it clear what this is for (and verify the right thing is happening automatically): https://github.com/brownplt/pyret-lang/blob/horizon/tests/pyret/tests/test-tables.arr#L653 You can see some similar style of...

I think this improves things, no reason to delay merging it.

Oh fascinating, good request. This ought to be doable.

A pretty specific type is synthed (https://github.com/brownplt/pyret-lang/blob/f1103c90388a6de3d3468ea48e67bf527f568d36/src/arr/compiler/type-check.arr#L1568), so the issue must be that in constraint solving the related error just gets called “an object type” – harder to track down;...

Right, I think that's what I was saying – in constraint solving, it fails on “is type variable `T` an object type” and gives an error with that constant string....

(@ds26gte and I just got a green build on a silly configuration error about starter vs. essentials in blocks. We caught it manually testing, but would be nice to not...