Louis Pilfold

This due to unfortunate ambiguity in the LSP specification. The manner in which autocompletions are inserted by the client is "open to interpretation". In future we will use the more...

I think it's that this editor is using `.` as the input boundary. I was hoping they'd instead match the whole prefix, but alas it seems not to be the...

Oh I see, I didn't realise you were reporting two problem. Could you open a second one with code examples for how the problem is triggered? Thank you.

Hey @ivanov ! That situation on the plane sounds really annoying, sorry about that. You're totally right, what you tried should have worked, and we want folks to be able...

Super useful, especially on the BEAM. We'll need to figure out a good design for this so let's start by researching what other languages do here. I though we had...

We need to do research and see what other languages and build tools do. > I think it would be useful if this feature also supported using ts-node to run...

A fab suggestion! We would need to implement #34 first before this type narrowing feature. I'm sure we had an existing issue for this but I can't find it now...

Hello! It would be good to fix this for sure, though it will be a bit fiddly.

Hello! It's not just a matter of purity, the VM only permits certain operations in guards for performance reasons. It is not possible to support arbitrary pure expressions. Purity tracking...

Hello! If we're unable to support both platforms then we'll have to defer that addition until we can. I don't have any particular opinions on the scope on this library...