Matthew Lutze
Matthew Lutze
> Because `OpSymUse` does not save its constituents I guess? Right. > But I still think it could just overwrite it with the new name. But then we get "can't...
> Update error message: "Unexpected effect parameter(s)". Also, it should not say tip in the explanation. Is this referring to the error about type parameters on effects?
> Do we want to ban unused effects? Yep, it's in the list. > Do we want to create a few separate ticket for the bigger items? Yes, I have...
I've explored this a little. There's of course some copy-pasting that would happen, for helper functions such as `Type.mkTuple`, but the amount of duplication doesn't seem totally unreasonable.
What happens when we have a mutable list of indexes? ```scala list[42] := "hello" list[42] := ref "hello" ``` Seems like it might get confusing.
> Why? Its always assignment to the LHS. Right, but are you assigning to ref at index `i` or replacing the ref at index `i`? > Does it get more...
> I'm not sure, if this is how it is supposed to be, but when hovering over a function imported from java, the message is a bit confusing with Pure...
This should affect: * [x] typechecking * [ ] redundancy checks * [x] error messages * [x] LSP information
We should also add this to the desugaring done in the `Weeder`. Currently `import ...(): SomeType & SomeEff` desugars to `... as SomeType & SomeEff` (a regular cast). Desugaring instead...
Depends on what you think of it. I think it's going in the right direction. There are a few things that can be cleaned up afterward, as I was trying...