Spotandjake

Thats valid but I feel like its not a confusing concept itself, docs would solve the issue and the feature matches the semantics of the language. Additionally we already have...

Is this still something we think we need? I'm not sure if preventing this at runtime would be the way we want todo this anymore, since this issue was made...

I did some digging on this and specifically it seems to be that the `pos_end` of the `pexp_loc` is one position behind in the nested binop case. That's at least...

> Thanks for doing this @spotandjake! I wonder if it is actually better to use this diff as a way for @ospencer and @peblair to inventory the usage of `dummy_loc`...

I updated the compiler walkthrough in #2092, I think we could consider closing this issue unless there's anything more we would like to add.

I'm not 100% sure this makes sense to implement. The use case for it would be making documentation more navigatiable but I feel like the issues aren't something we can...

> It looks like that JS_OF_OCAML stuff was added back in #4637 > > @phated are you guys limited to `-sWASM=0` in some fundamental way? i.e. is dropping the pure...

> > > It looks like that JS_OF_OCAML stuff was added back in #4637 > > > @phated are you guys limited to `-sWASM=0` in some fundamental way? i.e. is...

I think some questions we would need to address are: * When would these tests run (probably not ever commit to main) * What version range would we want to...

After discussing this a little more on discord it seems like the better solution is to convert `Box` to a record as: ```gr record Box { mut boxContent: a }...