ariel
Unsure about the immediate cause of constraint solving not completing here, but the type mismatches that you don't expect are another instance of expected types not behaving properly, which @hgoldstein...
> and can you guys fix self so when we make a function with : we can still identify self inside the parameters instead of self:unknown. There is an outstanding...
You could not possibly have tried the first option because we have not implemented shared self type inference. It is a future addition the language that we will develop to...
This is sort of a weird situation. The behavior in the old solver is actually mostly the same here, so this isn't particularly a "new solver" bug, but there is...
This issue occurs in both solvers, but we've been closing out fixed-by-old-solver stuff, so I've marked this as new-solver. A contribution that fixes it in both is welcome though.
I've edited your original post to appropriately format the code. You can read the source of the post again to see what the appropriate markdown syntax is for code. Please...
Please mention that you are using the new type solver explicitly in future bug reports.